Date: Wed, 15 Jan 2020 00:08:50 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: maintainer-feedback requested: [Bug 243358] [PATCH] lang/python*: DISABLED_EXTENSIONS doesn't work as advertised Message-ID: <bug-243358-21822-3E8iC7bJLj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243358-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-243358-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-python mailing list <python@FreeBSD.org> for maintainer-feedback: Bug 243358: [PATCH] lang/python*: DISABLED_EXTENSIONS doesn't work as advertised https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243358 --- Description --- I tried building lang/python38 on a system with sqlite3 available, and unfortunately it failed `check-plist` because the extension had been instal= led. Doing some grepping around, DISABLE_EXTENSIONS isn't actively referred to in setup.py nor in Makefile.pre*: ports/lang/python38/work/Python-3.8.1/setup.py:DISABLED_MODULE_LIST =3D [] ports/lang/python38/work/Python-3.8.1/setup.py: if ext.name not in DISABLED_MODULE_LIST] ports/lang/python38/work/Python-3.8.1/setup.py: sysconf_dis =3D sysconfig.get_config_var('MODDISABLED_NAMES').split() It turns out that the correct way to do this is via `Modules/Setup`, but th= is method seems to be broken. An upstream bug is pending for the issue.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243358-21822-3E8iC7bJLj>