At 04:44 PM 7/14/2005 +0100, Paul Moore wrote: >On 7/14/05, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > > At 10:26 AM 7/14/2005 +0100, Paul Moore wrote: > > >What I'm saying, is that I see a need for *another* transitional > > >process - enabling users and/or package authors to make their code > > >"resource safe", *without* having to buy into the egg/setuptools > > >transition. > > > > It still seems to me that you're missing something. If I don't care about > > eggs, why would I care about resource safety? Its only benefit is to allow > > my code to be put in an egg! :) > >You don't care about eggs (yet). Your users (one of whom is me) do, >and would like to package your code in an egg via python setup.py >--compiler-package=setuptools.command bdist_egg. This works fine, with >no source changes, but the resulting egg isn't zip-safe because of >resource usage issues. > >Your user (me) can maintain a small local patch to switch to the >resource API, but it would be nice to fold that patch into the >distribution, and so avoid the need for a local patch. But the patch >that is small for your user with setuptools installed, is large *for >you* because you don't (yet) buy into the benefits of eggs (and hence >the patch adds a dependency you don't want). So you reject the patch.
So give them a patch that's egg-safe *without* using pkg_resources! It'll be slightly more complicated to implement, but won't introduce *any* dependencies. Then use "easy_install -z" to force it into a zipped egg. Voila, you're done. _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
