Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #6035 > unrolled thread
| Started by | Ned Deily <nad@acm.org> |
|---|---|
| First post | 2011-05-22 21:01 -0700 |
| Last post | 2011-05-22 21:01 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Building Python: static library "3.2m" Ned Deily <nad@acm.org> - 2011-05-22 21:01 -0700
| From | Ned Deily <nad@acm.org> |
|---|---|
| Date | 2011-05-22 21:01 -0700 |
| Subject | Re: Building Python: static library "3.2m" |
| Message-ID | <mailman.1948.1306123306.9059.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web