Guido Guenther writes: > > So if you can't get the toy in exactly the way you want, you duplicate > > the source? sorry, I don't get it. > Crap. You refused to include it for 2.4 (#386738) and we'd need patches > to modify sys.path to use it in 2.5 either _although_ upstream agreed to > (hopefully) include it for 2.6. So why shouldn't I just package a useful > library to make it _easy_ and obvious to use in all python versions?
It's you talking crap. I don't modify upstream sources deliberately. AFAICR I asked you to get the change done upstream, then we can backport it to the package. I don't see agreement by upstream to include the module either. Could you point me to it? > > > We can drop this if > > > plistlib should get included upstream in 2.6: > > > > > > http://sourceforge.net/tracker/index.php?func=detail&aid=779460&group_id=5470&atid=105470 > > > > what about sending a patch upstream instead of brewing your own > > package? > See the above URL, the report is from 2003. You (thanks for that!) asked > for it too: > http://sourceforge.net/tracker/index.php?func=detail&aid=1565129&group_id=5470&atid=105470 so please show me the upstream approval and prepare a patch for current svn. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
