Re: What the deal with python3.5m.so and python3.5.so ??

From	eryk sun <eryksun@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: What the deal with python3.5m.so and python3.5.so ??
Date	2016-06-28 13:32 +0000
Message-ID	<mailman.77.1467120765.2358.python-list@python.org> (permalink)
References	<577256A6.7030509@chello.at> <CACL+1auASi6QL6zFppQDWoNDn94dv66VgTx5BF-BNqSNcXKHrQ@mail.gmail.com>

Show all headers | View raw

On Tue, Jun 28, 2016 at 10:51 AM, Steven Truppe <steven.truppe@chello.at> wrote:
>
> can someone tell me the difference between python3.5m.so and python3.5.so ??

The "m" suffix means that Python is configured "--with-pymalloc", i.e.
using specialized mallocs, including the small-object allocator. This
is the default configuration. You may also see a "dm" suffix for a
build that's configured "--with-pydebug" and "--with-pymalloc".

libpython3.5.so and libpython3.5m.so may actually link to the same
shared library:

    $ readlink libpython3.5.so
    ../../x86_64-linux-gnu/libpython3.5m.so.1

    $ readlink libpython3.5m.so
    ../../x86_64-linux-gnu/libpython3.5m.so.1

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

Thread

Re: What the deal with python3.5m.so and python3.5.so ?? eryk sun <eryksun@gmail.com> - 2016-06-28 13:32 +0000

csiph-web