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 vstinner
Recipients dom1310df, ezio.melotti, gvanrossum, malin, mrabarnett, serhiy.storchaka, vstinner
Date 2022-04-01.08:17:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1648801043.47.0.270071347932.issue47152@roundup.psfhosted.org>
In-reply-to
Content
sre_constants, sre_compile and sre_parse are not tested and are not documented. I don't consider them as public API currently.

If someone has good reason to use them, IMO we must clearly define which exact API is needed, properly document and test it.

If we expose something, I don't think that the API would be exposed as re.sre_xxx.xxx, but as re.xxx. 

I suggest to hide sre_xxx submodules by adding an underscore to their name. Moreover, the "sre_" prefix is now redundant. I suggest renaming:

* sre_constants => re._constants
* sre_compile => re._compile
* sre_parse => re._parse
History
Date User Action Args
2022-04-01 08:17:23vstinnersetrecipients: + vstinner, gvanrossum, ezio.melotti, mrabarnett, serhiy.storchaka, malin, dom1310df
2022-04-01 08:17:23vstinnersetmessageid: <1648801043.47.0.270071347932.issue47152@roundup.psfhosted.org>
2022-04-01 08:17:23vstinnerlinkissue47152 messages
2022-04-01 08:17:23vstinnercreate