Gaige Paulsen added the comment:
I can test the backports if you like. In that case, let me know when the
backports are done, I should be able to test those rapidly, now that I have my
build environment working for building from source.
Thanks again
Gaige Paulsen added the comment:
Sorry about the delay.
Finally fixed my workflow for building from scratch.
Result: I can confirm that the compilation problem is resolved with this change
(and was failing with the main branch prior to the change
Gaige Paulsen added the comment:
Short version is not yet. I spent time on it but ran into an issue getting the
full build on the machine I was building on. I expect to try it again before
the weekend.
Is there a binary copy of the framework from the CI somewhere? If so, I can
certainly do
Gaige Paulsen added the comment:
I'll try to check that in the next day or two.
--
___
Python tracker
<https://bugs.python.org/issue39026>
___
___
Python-bug
Gaige Paulsen added the comment:
Let me add my voice to those who ask to keep Solaris support in Python going
forward. We use SmartOS which is an Illumos and thus Solaris derivative.
We use Ansible extensively to automate our SmartOS deployments. We have a
couple hundred VMs and 2 part-time
Gaige Paulsen added the comment:
I should have been more specific. Sorry about that.
Yes, when including in Xcode, incorporating the framework. In
particular, I'm embedding 3.8 in an application (previously used the system
Framework, which was 2.7, which worked but Apple has warned
New submission from Gaige Paulsen :
The cpython/pystate.h includes cpython/initconfig.h using the relative path
"cpython/initconfig.h", which probably works fine if your include path
explicitly contains the top of the python directory, however when developing
with a framewor
