-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 16, 2008, at 12:52 PM, Brett Cannon wrote:
>On Sat, Aug 16, 2008 at 7:04 AM, Facundo Batista ><[EMAIL PROTECTED]> wrote: >> Hi! >> >> The issue 600362 has two patches (one for 2.6 and the other for 3.0) >> that are ready to commit (with a small change in the docs). This >> patches relocates the parse_qs and parse_qsl functions into the >> urlparse module (urllib.parse in 3k), bringing them from the cgi one. >> >> For backward compatibility, those functions are also accessible from >> the cgi module, but in the documentation says that the function was >> moved, and you should use it from the urlparse one. >> >> So, we don't have *any* change in the behaviour towards the final user. >> >> Two questions: >> >> - It's ok to do this now or we should wait for 3.1/2.7? >> >> - Should we add a deprecation warning in the cgi module for this functions? >> >> I propose to commit this now, but leave a deprecation warning for the >> next release. >> > >Obviously Barry's call, but I think it's fine to do what you are proposing. I think it's fine to commit this. I would put a DeprecationWarning in 3.0 and a PendingDeprecationWarning in 2.6 (updated to a DW in 2.7). - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIqja42YZpQepbvXERAp7oAJ9t6h/MtzAQQDDS3J65p7Zwpf+JzgCeO24r kCmcTtPIeo/M0hiqmtee0/o= =FVuq -----END PGP SIGNATURE----- _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
