Greg Ewing <greg.ewing <at> canterbury.ac.nz> writes: > > The main point of the __pycache__ proposal is to solve the needs of > > Ubuntu/Debian packagers. If you are developing (rather than deploying or > > building packages), you shouldn't have these needs AFAICT. > > Maybe it's one point, but I'm not sure it's the *main* one. It's the only reason the PEP was originally designed, and proposed. > Personally I would benefit most from it during development. Why? What benefit would it bring to you? > I hardly ever look in the directories of installed packages, > so I don't care what they look like. Neither do I, but Ubuntu/Debian packagers want to share the source code of third-party libraries across Python versions while keeping distinct bytecode files (obviously). Again, that's the original point of the PEP as proposed by Barry.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4