[Python-Dev] [Python-3000] parse_qs and parse_qsl functions (original) (raw)

Barry Warsaw barry at python.org
Tue Aug 19 04:57:33 CEST 2008

-----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 <facundobatista at gmail.com> 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 parseqs and parseqsl 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).

iD8DBQFIqja42YZpQepbvXERAp7oAJ9t6h/MtzAQQDDS3J65p7Zwpf+JzgCeO24r kCmcTtPIeo/M0hiqmtee0/o= =FVuq -----END PGP SIGNATURE-----

More information about the Python-Dev mailing list