Message122792
| Author |
amaury.forgeotdarc |
| Recipients |
Arfrever, amaury.forgeotdarc, barry, doko, eric.araujo |
| Date |
2010年11月29日.12:10:28 |
| SpamBayes Score |
2.4431351e-06 |
| Marked as misclassified |
No |
| Message-id |
<1291032630.21.0.90300627044.issue10262@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I agree with the intent: package maintainers, or people compiling python for their own need, should have the right to choose the suffix used by extension modules.
I suggest another option though, one that directly sets the SOABI used in extension file names. This would override both the default SOABI (python3.2) and the flags added to it.
For example, when no flag is passed to ./configure, the default is equivalent to
--soabi=cpython3.2m
And we can get the 2.x naming scheme back simply with:
--soabi=
Yes, this flag should be only used when you know what you are doing. This builds a version of python that will be unable to load extensions built by other people. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年11月29日 12:10:30 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, barry, doko, eric.araujo, Arfrever |
| 2010年11月29日 12:10:30 | amaury.forgeotdarc | set | messageid: <1291032630.21.0.90300627044.issue10262@psf.upfronthosting.co.za> |
| 2010年11月29日 12:10:28 | amaury.forgeotdarc | link | issue10262 messages |
| 2010年11月29日 12:10:28 | amaury.forgeotdarc | create |
|