[Slackbuilds-users] /usr/include/python3.7 or 3.7m ?

MyRequiem mrvladislavovich at gmail.com
Fri Apr 24 08:51:10 UTC 2020

Re: Christoph Willing 24.04.2020 <74588ed6-9214-79c1-3b2b-9fb252a5779d at linux.com>
>At the moment, SBo builds of python3 on both my daily machine and a
>clean VM result in the include files being placed into
>/usr/include/python3.7m (rather than a plain /usr/include/python3.7).
>Apparently the different paths signified use (or non-use) of an internal
>memory allocator which is on by default but controllable using the
>--with(out)-pymalloc configure option when building python3. I've tested
>this and the --without-pymalloc does result in /usr/include/pyton3.7
>(not python3.7m).
>BTW this behaviour has changed in 3.8 where everything goes into
>/usr/include/pyton3.8 (see -current, also see
>Before proceeding here with a complaint about other packages wrongly
>hard coding  python-related .h files into /usr/include/python3.7, rather
>than python3.7m, could people first confirm that their python3
>installation is using /usr/include/python3.7m, as mine does, please?
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
Python3.7: /usr/include/python3.7m
Python3.8: /usr/include/python3.8

More information about the SlackBuilds-users mailing list