[Bug 243937] lang/python38: Fails to package in certain conditions due to DISABLED_EXTENSIONS not working

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243937

--- Comment #6 from John Hein <jcfyecrayz at liamekaens.com> ---
(In reply to Kubilay Kocak from comment #5)
python37 has patch-issue20210 to "solve" how to disable building/installing the
extensions.  That got repocopied from python36 and python35/34 before that. 
You probably already know this.

I don't know why it was not pulled into python38.  Maybe the patch no longer
applied?  I didn't check.  But from reading the upstream issue 20210, it's
clear they went another way than the original patch we've been carrying along. 
The  *disabled* marker method in Modules/Setup* was committed (looks like it
was committed in python37 in 2017).  So I think using that going forward is the
right way to go (instead of trying to resurrect the old patch which upstream
decided not to use).

I just read bug 241416.  The extensions problem was known and deferred (until
someone could develop the fix).  So I guess it just hadn't gotten addressed
yet.

I think (but have not tried) that this patch would work for our latest
python37.  We could choose to apply it there as well or just live with the old
patch as long as it still works.  pro for the new patch in python37: future
python37 updates might break the old patch.  con argument: unnecessary
work/thrash (wait until current flavor stops working for py37, if ever).  In
any case, that decision can be separated from this fix for py38.

Re: your second question re: third party headers.  I don't know if having gdbm,
et. al., ports installed before building py38 affects whether those extensions
are built or not.  I suspect it does, but I have not done that test to confirm.
 In my environment, they were installed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.