<antocuni>
I think it is better to create another user, e.g. "pypy.wheelbuilder", and add it as a maintainer. This way nobody has to put its own personal password on travis
<antocuni>
the question is, which email should I use to create it? pypy-z? Or we create a special wheelbuilder@pypy.org?
<antocuni>
I said "pypy.wheelbuilder" instead of "vmprof.wheelbuilder" because this way we can use it for more than one project (e.g. cffi)
xcm has quit [Remote host closed the connection]
xcm has joined #pypy
mvantellingen has quit [Ping timeout: 252 seconds]
<fijal>
cfbolz: I still claim that overspecific tests that are hard to maintain but actually don't test much are worse than no tests at all ;-)
mvantellingen has quit [Ping timeout: 252 seconds]
mvantellingen has joined #pypy
antocuni has quit [Ping timeout: 258 seconds]
marky1991_2 has quit [Quit: Saliendo]
jacob22 has quit [Ping timeout: 252 seconds]
jacob22 has joined #pypy
Rhy0lite has quit [Quit: Leaving]
marky1991 has joined #pypy
fryguybo1 has quit [Read error: Connection reset by peer]
Ai9zO5AP has quit [Quit: WeeChat 2.4]
fryguybob has joined #pypy
<kenaan>
mattip py3.6 51716b155429 /pypy/module/_codecs/test/test_codecs.py: skip test that only works translated
<kenaan>
mattip py3.6 8c02125cb1c5 /pypy/objspace/std/unicodeobject.py: win32, python2 doesn't like surrogates, skip this check
Ai9zO5AP has joined #pypy
marky1991 has quit [Ping timeout: 246 seconds]
<tos9>
mattip: FWIW I didn't forget about numpy stuff, just "luckily" now I can't actually *re-break* things so I can confirm what fixed it :/
<tos9>
I am fairly sure that homebrew changed some stuff recently vis-a-vis binutils (they stopped linking it and made it keg only)
<tos9>
So now I think I have to go out of my way to probably make my system look like what I think it looked like a few weeks ago before they changed the formula
<tos9>
But yeah homebrew is really :((( sometimes.
<mattip>
well, it is fine to close the issue as "no longer reproducible"
<tos9>
I think it *is* reproducible because of the way homebrew works there -- basically it doesn't migrate systems that it linked the formula on
<tos9>
So e.g. one set of users I suspect will run into those errors are if you installed binutils like 6 months ago
<tos9>
then homebrew, even though it changed the formula, does not go and unlink the original binaries
<tos9>
But I think e.g. glyph was one of the people that commented on the ticket, so maybe I can just check with him to see if he still is seeing errors
<glyph>
yo
<glyph>
what do you need me to check
<tos9>
aloha
<tos9>
glyph: Were you having issues getting numpy installed on macOS+pypy
<tos9>
glyph: And if so, what does this command do for you: `rm -rf venv; virtualenv -p pypy3 venv; MACOSX_DEPLOYMENT_TARGET=10.14 venv/bin/python -m pip install --no-cache numpy`
<glyph>
I definitely was
<glyph>
I have a meeting in 5 minutes
* mattip
zzz
<glyph>
I'll happily check that command afterwards though
<tos9>
Yup cool.
<kenaan>
mattip py3.6 95ef57b94c9d /pypy/module/posix/: fixes for win32
<kenaan>
mattip win32-encoding 51a97447c69a /pypy/module/sys/: start to use filesystemencoderrors