3 ms·
I'm disappointed to see so many negative HN comments about this project. I think it is really cool! You shouldn't use this in a production web service--and the
by jamesmishra 6y ago
I'm disappointed to see so many negative HN comments about this project. I think it is really cool!
You shouldn't use this in a production web service--and the author says as much in the README--I think there are some great uses for this code:
1. Demonstrating how the Python import system works. There is a lot of nuance at hand that other programming languages (like C) don't have an analogy for.
2. Creating truly self-contained Jupyter notebooks. Right now, if I want to send someone a working Jupyter notebook, I have to send them a requirements.txt (or, better yet, a Dockerfile) for them to install in a virtualenv. This is too bad, because specifying the dependencies in the notebook itself is better for teaching purposes.
- nemosaltat 6y agoRe: 2, IMO this is where makefiles shine. When I got my start on Linux with Ubuntu (Breezy Badger IIRC) I compiled many (most?) of the utilities I wanted from source. When `make` didn’t “JustWorkTM”, it give very clear reasons why, and even as a noob I could usually correct the issue. Python , Docker, and NodeJS etc still leave much to be desired in that regard.
- rbanffy 6y agoI'm concerned people will take it as a good idea instead of a demonstration of what can, but shouldn't, be done.
- Nullabillity 6y agoSadly, this is already a thing in a relatively common JS bundler..[0] :/ [0]: https://en.parceljs.org/hmr.html#automagically-installed-dependencies https://en.parceljs.org/hmr.html#automagically-installed-dep...
- Kaze404 6y ago> This only occurs in development (using serve or watch), however in production (using build) autoinstall is disabled to prevent unwanted side-effects on deployment. > You can disable this feature using --no-autoinstall. Seems fine to me.