cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end ) | use cffi for calling C | if a pep adds a mere 25-30 [C-API] functions or so, it's a drop in the ocean (cough) - Armin
<mattip>
cd lib_pypy; ../path/to/pypy _ssl_build.py
<mattip>
which should verbosely (sic?) report the gcc command used, and it should include MACOSX_DEPLOYMENT_TARGET
<mgorny>
mattip: when working on stdlib update, should i create the integration branch per instructions or just a topic and let you do the branches?
<YannickJadoul>
mattip: Thanks for the quick help, as always :-) Should we update our tests to run on 10.14, then, or do you wish to try a few other things?
<mattip>
mgorny: please do not use a topic branch, since we will want to run on the buildbots before merging
<mattip>
you can use what I did around e888dd32ae03 to update py3.7 to 3.7.9
<mattip>
I created a stdlib3.7.9 branch with a single meaningless commit so I could run the buildbots on it
<mattip>
which then gave me a baseline for comparison to see how many new errors there were
<mattip>
probably not needed for default, since there should be no errors in the first place
<mattip>
so you can go ahead and update the vendor/stdlib-2.7 (accepting the new versions of the files)
<mattip>
to sync it with CPython2.7,
<mattip>
then create a branch off default, say stdlib-2.7.16, and merge vendor/stdlib-2.7 into it
<mattip>
and then start running tests
<mattip>
YannickJadoul: up to you. If your users are still on <=10.13, you might want to stick with the previous release until we work out what is wrong
<mgorny>
ok
<mattip>
whohoo, 15 minutes of glory on hacker new's front page
<YannickJadoul>
mattip: Right, let's see what the others think :-)
<mattip>
and even some nice comments too
<YannickJadoul>
Congrats! :)
<mattip>
I guess we _should_ migrate speed.pypy.org to show python3 benchmarks on the summary
oberstet has quit [Quit: Leaving]
<mgorny>
mattip: should i mark wheel updates (i.e. from lib-python/2.7/ensurepip/_bundled/pip-18.1-py2.py3-none-any.whl to lib-python/2.7/ensurepip/_bundled/pip-19.2.3-py2.py3-none-any.whl) as copies or just remove/add?
<mgorny>
i suppose copy doesn't give any real benefit here
<mattip>
as for ensurepip specifically, I would prefer to stay with the versions we have anyway
<mattip>
since the newer ones allows people to install manylinux2010/manylinxu2014 wheels
<mattip>
although admittedly the chances of anyone creating modern wheels for python2.7 is quite slim
<mgorny>
i suppose i can try undoing the update as part of integration branch
<mgorny>
mattip: i'm a bit confused now. it seems that stdlib-2.7.16 branch hasn't been merged to master?
<mgorny>
or at least in merge conflicts it seems that default is older in cProfile.py
<agronholm>
where's the hacker news article?
<agronholm>
nvm, found it
<mattip>
ahh, we already have a stdlib-2.7.16 branch? So I am confused too
<mattip>
someone (me?) must have started the job and never finished
<mattip>
feel free to override it and start again if it is easier
* mattip
bbl
mattip has quit [Remote host closed the connection]