Don Question wrote: > maybe it's because gtk and therefore pygtk is an almost "linux only" > thing.
I personally know and work with a fair number of people who need to develop with pygtk on OSX. > Even if you include our bsd-friends, there is no real need for an > alien "quick and dirty" packaging system like the egg infrastructure. Eggs aren't that quick and dirty, actually. I do see where resentment about specifics of the setuptools package come from, but that doesn't say much about eggs as a concept. There are other systems than setuptools that work with eggs and their metadata. > The > native "sophisticated" software-managment-systems just provides too many > benefits. But there are environments where they just don't fit in the established workflow, which isn't a judgement of the relative merits of installation systems or package managers but just a matter of needing to use packages together that each use a different packaging system. As an example, if pygtk was installable as an egg, dependencies of other packages on pygtk could be expressed in the same way that dependencies on other projects can be expressed - by listing its egg name in an appropriate metadata field. pygtk is among the most important of those odd beasts that always need some special treatment (even if it's just telling people to use the system's Python and first install pygtk using their system's package manager before doing whatever they normally do when working with a Python package). Even if eggs sucked (which they don't), they're still an established standard in the Python community, so there's value in providing Python libraries in that format. Note that formulating the setup code for a project such that an egg of that project can be built doesn't mean any other packaging has to be abandoned. It's mainly just a matter of adding the appropriate metadata. > Eggs are nice and good, but maybe not just for every situation. And maybe > pygtk is not an "useful" egg. I know a number of developers who would be very happy about a pygtk egg. -- Thomas _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
