Having used JARs with Java, I think
PythonEggs is a great idea. And, as of PyCon 2005, it seems it's a lot less of an idea and more of an implementation.
[permalink] [3 comments] 22.03.2005, 20:45
Filed under: python
- Comments:
Posted by Mark Eichin at 22.03.2005, 22:39
Having seen how badly "gems" work in ruby, I'm deeply suspicious, but as long as they "hide" everything so that an application still *only* calls import and can't *tell* if it's coming from an Egg or a native package, that'll be acceptable.(Of course, from the packaging side of things, I'm dismayed by Jars as well, given the number of version skew problems I've seen them cause.)
Posted by Jarno Virtanen at 23.03.2005, 07:44
Yeah, but I've worked with systems where I don't have access to command line p-y-t-h-o-n so I can't run 'setup.py install' and Jar-like system would be a heaven there. But, sure, there are problems with versioning and other things.
Posted by Phillip J. Eby at 29.03.2005, 07:12
If you want to manage dependencies with a completely oblivious application, you'll have to add the eggs you want to PYTHONPATH. Once we've finished the runtime, inter-egg dependencies will be managed via metadata. But, for the top-level application, stuff will either have to be on PYTHONPATH/sys.path or you'll have to call a function to say, "I'd like Twisted>=1.2 on my path please."Anyway, there are a variety of ways to control what eggs end up on the path.