This is compounded with the fact that a properly configured version control system will only push .py files to the central repository, not .pyc files, meaning that your code can pass the "import test" (does everything import okay) just fine and not work on anyone else's computer. Second,...
If you're interested in CPython specifically: it compiles the source files into a Python-specific lower-level form (known as "bytecode"), does so automatically when needed (when there is no bytecode file corresponding to a source file, or the bytecode file is older than the source or c...
we build fat packages (meaning, they contain lots of stuff, which might not be used for one thing or the other) So the pyc compilation process actually adds alot of overhead to deploying jobs, also, pacakge builds break if we have invalid python in the package thanksContributor...
You can set sys.dont_write_bytecode = True in your source, but that would have to be in the first python file loaded. If you execute python somefile.py then you will not get somefile.pyc. When you install a utility using setup.py and entry_points= you will have set sys.dont_write...