whats the difference between python 3.3 and 3.3m
Question:
What’s the difference between python 3.3 and 3.3m
I’m using Ubuntu 13.04 Raring and on my system I have python2.7 and python3.3 (I know the differences between 2 and 3)
But I also have installed python3.3m (and it’s not a symlink to 3.3). So what does the m stand for?
Answers:
python3 is a symbolic link to python3.3
python3.3 is a hard link to python3.3m
And as @nneonneo ‘s answer indicating, The m suffix means specifically a “pymalloc” build of Python. Then the links do what they do.
The m suffix means specifically a “pymalloc” build of Python, and it may mean that the ABI of 3.3 on your platform is not the same as the ABI of 3.3m. Extension modules must be built for the specific ABI in question. This means that 3.3 extension modules won’t work with 3.3m and vice-versa.
The change to tag Python versions was proposed and accepted as PEP-3149: ABI version tagged .so files.
What’s the difference between python 3.3 and 3.3m
I’m using Ubuntu 13.04 Raring and on my system I have python2.7 and python3.3 (I know the differences between 2 and 3)
But I also have installed python3.3m (and it’s not a symlink to 3.3). So what does the m stand for?
python3 is a symbolic link to python3.3
python3.3 is a hard link to python3.3m
And as @nneonneo ‘s answer indicating, The m suffix means specifically a “pymalloc” build of Python. Then the links do what they do.
The m suffix means specifically a “pymalloc” build of Python, and it may mean that the ABI of 3.3 on your platform is not the same as the ABI of 3.3m. Extension modules must be built for the specific ABI in question. This means that 3.3 extension modules won’t work with 3.3m and vice-versa.
The change to tag Python versions was proposed and accepted as PEP-3149: ABI version tagged .so files.