On Sun, Nov 18, 2012 at 8:54 PM, Kristján Valur Jónsson < kristjan at ccpgames.com> wrote: > I don't have a well formed solution in mind, but I would see it desirable > to have a way for someone to release his package with all its dependencies > as a self-contained and isolated unit. E.g. if package foo.py relies on > functionality from version 1.7 of bar.py, then that functionality could be > bottled up for foo´s exclusive usage. > Another package, baz.py, could then also make use of bar, but version 1.8. > The two bar versions would be isolated. > > Perhaps this is just a pipedream. Even unpossible. But it doesn't harm > to try to think about better ways to do things. > > Easily bundling dependencies is a key principle behind the ability to execute directories and zipfiles that contain a top level __main__.py file that was added back in 2.6 (although the zipfile version doesn't play nicely with extension modules). Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20121118/e0da2c51/attachment.html>
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