On Tue, 28 Jul 2009 11:50:00 +0100, Paul Moore <p.f.moore at gmail.com> wrote: > egg_info data is in to allow "standard" (setup.py install and hence OS > package manager managed) packages to provide metadata in a > discoverable way. Using a format that is (reasonably) compatible with > setuptools is simply a matter of co-operating with existing de facto > standards. > > Eggs themselves (as a distribution format) are just zip files with a > funny extension, and as such are supported by Python. ok - I get it..... It's all one big monty python comedy thing where things are quirky and inconsistent - there's little continuety from one scene to the next but you have to stop sometimes and have a laugh... because to word quote from you - "funny" Your whole email whilst perphaps technically correct is terribly difficult for a software engineering person to follow. Monty python was only meant to be a funny film for entertainment, not a philosophy for building software from.... Why we can have the egg_info without allowing the egg is kind of like having a chicken and egg story without allowing the chicken.. or is it the egg.. oh I lost track... I think I need to watch the movie again to understand what's happening here... Let me go away confused... don't ask me any more questions or elaborate with more answers. Thanks. :-) David
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