> if you're doing anything serious for production then the environment should be containerized.
What do you mean?
What do you mean?
When you build and package things for production you should create an environment. This ensures the packaging the right versioning of requirements for build.
Say you build using the system version but use packages based on another version. It may work for you but probably won’t work elsewhere.
The problem comes about when someone does the following:
- creates python project
- pip install some_package
- import some_package
Turns out some package was already in the path but a different version
- proceeds to test and build with the assumption of some_package @ newer
- all tests pass
- ships project with requirements of some_package @ newer
Someone attempts to use the package but it doesn’t work.
That’s what doesn’t pass muster to me. Why should I work on my CSS styles in an environment with the production database? It will be much slower than just working on that package in my desktop environment with just enough scaffolding the code runs.
But maybe I’m not understanding your suggestion.
What does connecting to a production DB have to do with any of that?