[Python-Dev] Handling deprecations in the face of PEP 384 (original) (raw)
Brett Cannon brett at python.org
Sat Apr 21 03:59:21 CEST 2012
- Previous message: [Python-Dev] [Python-checkins] cpython: Issue #14581: Windows users are allowed to import modules w/o taking
- Next message: [Python-Dev] Handling deprecations in the face of PEP 384
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
As I clean up Python/import.c and move much of its functionality into Lib/imp.py, I am about to run into some stuff that was not kept private to the file. Specifically, I have PyImport_GetMagicTag() and NullImporter_Type which I would like to chop out and move to Lib/imp.py.
From my reading of PEP 384 that means I would need to at least deprecate PyImport_getMagicTag(), correct (assuming I follow through with this; I might not bother)? What about NullImporter_Type (it lacks a Py prefix so I am not sure if this is considered public or not)? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120420/033de166/attachment.html>
- Previous message: [Python-Dev] [Python-checkins] cpython: Issue #14581: Windows users are allowed to import modules w/o taking
- Next message: [Python-Dev] Handling deprecations in the face of PEP 384
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]