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

Dave Woodfall dave at slackbuilds.org
Fri Apr 24 12:24:53 UTC 2020

On 2020-04-24 22:18,
Christoph Willing <chris.willing at linux.com> put forth the proposition:
> On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote:
> > i've a reasonable collection of python .sbo packages installed, and
> > sip.h is the only file in /usr/include/python3.7
> > which is from stock slackware 14.2 sip-4.18 package
> > Regards, Tim
> >
> Thanks all for the replies confirming the python3 include directories.
> Tim, I think you mean /usr/include/python2.7 for the sip.h from stock
> Slackware sip-4.18-x86_64-1 package?
> If you have a /usr/include/python3.7/sip.h (the one which should be in
> /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild.
> I emailed the maintainer a few days ago with a version-independent
> method to install in the correct location but haven't heard back about
> it yet (so cc'd here now as a reminder). I just thought I should also
> check here in case there was something whacky about my own setup but
> based on the feedback, as well as noticing that AlienBob's python3
> package uses /usr/include/python3.7m, I"m sure now that the problem is
> with the python3-sip SlackBuild. It looks very close to the SlackBuild
> in -current but of course -current uses python 3.8 where the issue has
> been fixed, rather than python 3.7 as on SBo.
> chris

I maintain python3-sip now, so if we are all in agreement that we use
python3.7 I'll fix that this week.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200424/66d5cd43/attachment-0001.asc>

More information about the SlackBuilds-users mailing list