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 rhdv
Recipients christian.heimes, pitrou, r.david.murray, rhdv, serhiy.storchaka, shashank
Date 2012-11-04.14:28:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352039326.41.0.616158954811.issue10030@psf.upfronthosting.co.za>
In-reply-to
Content
If the encryption is so horrible why is there any support (with bad performance) at all in Python?
It would be better to remove it altogether.
This prevents users from building software using this feature only to find out later how bad the performance is. (This is the main reason why I have submitted this patch.)
If the support had not been in Python I would not have used this feature to begin with.

To reiterate my previous point. Either support something and do it well, or don't. Don't do a half job.

Please note that there are more attempts to fix this, so I am not completely alone here.
http://pypi.python.org/pypi/czipfile
History
Date User Action Args
2012-11-04 14:28:46rhdvsetrecipients: + rhdv, pitrou, christian.heimes, r.david.murray, shashank, serhiy.storchaka
2012-11-04 14:28:46rhdvsetmessageid: <1352039326.41.0.616158954811.issue10030@psf.upfronthosting.co.za>
2012-11-04 14:28:46rhdvlinkissue10030 messages
2012-11-04 14:28:46rhdvcreate