Hi, I know that the deadline for module removal is now passed, but I think we forgot to decide what should happen to the deprecated sre module:
import sre :1: DeprecationWarning: The sre module is deprecated, please import re. help(sre) ... DESCRIPTION This file is only retained for backwards compatibility. It will be removed in the future. sre was moved to re in version 2.5. ...
Currently, the sre module is just a stub that imports the re module. So, I don't think removing in Py3k will cause any problem. Cheers, -- Alexandre
On Mon, May 5, 2008 at 3:35 PM, Alexandre Vassalotti
Hi,
I know that the deadline for module removal is now passed, but I think we forgot to decide what should happen to the deprecated sre module:
import sre :1: DeprecationWarning: The sre module is deprecated, please import re. help(sre) ... DESCRIPTION This file is only retained for backwards compatibility. It will be removed in the future. sre was moved to re in version 2.5. ...
Currently, the sre module is just a stub that imports the re module. So, I don't think removing in Py3k will cause any problem.
I just added it to to the PEP for removal. -Brett
On Mon, May 5, 2008 at 5:35 PM, Alexandre Vassalotti
Currently, the sre module is just a stub that imports the re module. So, I don't think removing in Py3k will cause any problem.
Is this just the sre.py module? Does it include sre_constants, sre_compile, and sre_parse? -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1."
On Wed, May 7, 2008 at 6:50 PM, Christian Heimes
Brett Cannon schrieb:
I just added it to to the PEP for removal.
Who is going to rewrite json.scanner? It's using sre.
Christian
You mean the sre_parse, sre_compile and sre_constants, right? Because the sre module is currently empty (it just imports stuff from re). -- Alexandre
On Wed, May 7, 2008 at 8:03 PM, Alexandre Vassalotti
On Wed, May 7, 2008 at 6:50 PM, Christian Heimes
wrote: Who is going to rewrite json.scanner? It's using sre.
Christian
You mean the sre_parse, sre_compile and sre_constants, right? Because the sre module is currently empty (it just imports stuff from re).
Yes. -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1."
On Wed, May 7, 2008 at 7:12 PM, Benjamin Peterson
On Mon, May 5, 2008 at 5:35 PM, Alexandre Vassalotti
wrote: Currently, the sre module is just a stub that imports the re module. So, I don't think removing in Py3k will cause any problem.
Is this just the sre.py module? Does it include sre_constants, sre_compile, and sre_parse?
I was talking only about the sre module stub, not the other sre_* modules. These are still needed (e.g., sre_constants is used to generate the Modules/sre_constants.h header). Anyway, would it be a good idea to move the re and sre_* modules into their own package? re -> re.__init__ sre_compile -> re._compile sre_constants -> re._constants sre_parse -> re._parse -- Alexandre
On Wed, May 7, 2008 at 6:20 PM, Alexandre Vassalotti
On Wed, May 7, 2008 at 7:12 PM, Benjamin Peterson
wrote: On Mon, May 5, 2008 at 5:35 PM, Alexandre Vassalotti
wrote: Currently, the sre module is just a stub that imports the re module. So, I don't think removing in Py3k will cause any problem.
Is this just the sre.py module? Does it include sre_constants, sre_compile, and sre_parse?
I was talking only about the sre module stub, not the other sre_* modules. These are still needed (e.g., sre_constants is used to generate the Modules/sre_constants.h header).
Anyway, would it be a good idea to move the re and sre_* modules into their own package?
re -> re.__init__ sre_compile -> re._compile sre_constants -> re._constants sre_parse -> re._parse
That's a possibility, although this will have to go past python-dev at this point since the PEP has already been accepted. -Brett
participants (4)
-
Alexandre Vassalotti
-
Benjamin Peterson
-
Brett Cannon
-
Christian Heimes