Re: Building Python: static library "3.2m"

From	Ned Deily <nad@acm.org>
Subject	Re: Building Python: static library "3.2m"
Date	2011-05-22 21:01 -0700
References	<BANLkTi=T+tXTOAdN2ts7RXpNcqaUFnO_iQ@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.1948.1306123306.9059.python-list@python.org> (permalink)

Show all headers | View raw

In article <BANLkTi=T+tXTOAdN2ts7RXpNcqaUFnO_iQ@mail.gmail.com>,
 Chris Angelico <rosuav@gmail.com> wrote:
> Question: Why "3.2m"? What does that m mean? It seems to have come up
> a couple of times in the build process.

It's a new feature in Python 3.2 to allow multiple versions of shared C 
object files that differ in configure options (i.e. ones that affect the 
Python C ABI) to co-exist in one Python installation.  "m" means that 
they were built with pymalloc.  Other flags are "d" for debug, and "u" 
for wide-unicode.

http://docs.python.org/py3k/whatsnew/3.2.html#pep-3149-abi-version-tagged
-so-files

-- 
 Ned Deily,
 nad@acm.org

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Building Python: static library "3.2m" Ned Deily <nad@acm.org> - 2011-05-22 21:01 -0700

csiph-web