4 ms·
Mostly agree, however the only area I think the “official” tools could improve upon is split dependencies between requirements.txt (top level requirements), dev
by samwillis 4y ago
Mostly agree, however the only area I think the “official” tools could improve upon is split dependencies between requirements.txt (top level requirements), dev-requirements.txt (top level dev only requirements), and requirements-freeze.txt (all requirements versions frozen for deployment). Currently you have to be careful to ensure your requirements-freeze.txt doesn’t end up with dev dependency’s in it.
- fxtentacle 4y agoIn the industries where I worked as a C++ coder, it was quite common to leave debugging symbols in the binaries so that customers could have better stack traces for their error diagnostics. On OS X, it is still quite common to ship production apps in a way that allows you to "symbolicate" stack dumps after the fact. What I'm trying to say: In most production uses, the line between dev and release dependencies is so blurred that it almost doesn't exist.