[New-bugs-announce] [issue15242] PyImport_GetMagicTag() should use the same const char * as sys.implementation.cache_tag
Eric Snow
report at bugs.python.org
Tue Jul 3 08:54:12 CEST 2012
New submission from Eric Snow <ericsnowcurrently at gmail.com>:
There was some concern with PyImport_GetMagicTag() extracting its value from sys.implementation.cache_tag. One solution is to have the two use a common underlying value. However, that's basically what was already in import.c and I'd rather minimize that file at this point.
An alternative is to have the underlying value defined in a more amenable spot, but I'm not convinced that buys a whole lot over simply exposing the underlying value in PyImport_GetMagicTag(). If we could deprecate that function...
Another possibility is to move the underlying value to configure. The down-side is that it's platform-specific. I've attached a patch that does this. While it may do too much as-is, it demonstrates my point.
----------
components: Interpreter Core
files: cache_tag_via_configure.diff
keywords: patch
messages: 164582
nosy: amaury.forgeotdarc, brett.cannon, eric.snow
priority: normal
severity: normal
stage: patch review
status: open
title: PyImport_GetMagicTag() should use the same const char * as sys.implementation.cache_tag
type: behavior
versions: Python 3.3
Added file: http://bugs.python.org/file26237/cache_tag_via_configure.diff
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15242>
_______________________________________
More information about the New-bugs-announce
mailing list