Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #110694 > unrolled thread

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

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.

Contents

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

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

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

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web