python 3.x - Difference between python3 and python3m executables -

what difference between /usr/bin/python3 , /usr/bin/python3m executibles?

i observing them on ubuntu 13.04, google suggests exist on other distributions too.

the 2 files have same md5sum, not seem symbolic links or hard links; 2 files have different inode numbers returned ls -li , testing find -xdev -samefile /usr/bin/python3.3 not return other files.

someone asked similar question on askubuntu, wanted find out more difference between 2 files.

credit goes chepner pointing out had link solution.

python implementations may include additional flags in file name tag appropriate. example, on posix systems these flags contribute file name:

--with-pydebug (flag: d)

--with-pymalloc (flag: m)

--with-wide-unicode (flag: u)

via pep 3149.

regarding m flag specifically, pymalloc is:

pymalloc, specialized object allocator written vladimir marangozov, feature added python 2.1. pymalloc intended faster system malloc() , have less memory overhead allocation patterns typical of python programs. allocator uses c's malloc() function large pools of memory , fulfills smaller memory requests these pools.

via what's new in python 2.3

finally, 2 files may hardlinked on systems. while 2 files have different inode numbers on ubuntu 13.04 system (thus different files), comp.lang.python post 2 years ago shows once hardlinked.