Message164582
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. |
|
Date |
User |
Action |
Args |
2012-07-03 06:54:13 | eric.snow | set | recipients:
+ eric.snow, brett.cannon, amaury.forgeotdarc |
2012-07-03 06:54:12 | eric.snow | set | messageid: <1341298452.58.0.698952095948.issue15242@psf.upfronthosting.co.za> |
2012-07-03 06:54:06 | eric.snow | link | issue15242 messages |
2012-07-03 06:54:06 | eric.snow | create | |
|