Message 78160 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	faw
Recipients	faw, koen
Date	2008-12-21.23:03:26
SpamBayes Score	4.8784e-08
Marked as misclassified	No
Message-id	<1229900608.76.0.344807729934.issue4710@psf.upfronthosting.co.za>
In-reply-to

Content
I'm not sure if it would make sense to save current extract()/extractall() behaviour and implement new with another function because current one is simply faulty. And if it's about BC breaks then well... it may be introduced in 3.0 line, I think that leaving faulty behaviour and introducing another with another function misses the point. AFAIK there'd be no problem with Windows-style paths but to be sure I revised my patch. Yes, I'm sorry for the lack of tests, it is my first patch and I forgot about this. I'll write them in a couple of hours.

I'm not sure if it would make sense to save current
extract()/extractall() behaviour and implement new with another function
because current one is simply faulty. And if it's about BC breaks then
well... it may be introduced in 3.0 line, I think that leaving faulty
behaviour and introducing another with another function misses the point.

AFAIK there'd be no problem with Windows-style paths but to be sure I
revised my patch.

Yes, I'm sorry for the lack of tests, it is my first patch and I forgot
about this. I'll write them in a couple of hours.

History
Date	User	Action	Args
2008-12-21 23:03:28	faw	set	recipients: + faw, koen
2008-12-21 23:03:28	faw	set	messageid: <1229900608.76.0.344807729934.issue4710@psf.upfronthosting.co.za>
2008-12-21 23:03:28	faw	link	issue4710 messages
2008-12-21 23:03:27	faw	create