cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake https://pypy.org | IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end and https://libera.irclog.whitequark.org/pypy | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
epony has joined #pypy
<cfbolz> arigato: you can also work in exactly the same way as you used to with hg, on github: just push. either directly to main/py3.9/py3.10, or your branches and merge them on the commandline
<cfbolz> arigato: and we can decide how lenient we want to be with giving people the necessary permissions, we have had rather good experiences with being very permissive in the past
jcea has joined #pypy
<LarstiQ> ah, the github move is live
Dejan has joined #pypy
jcea has quit [Ping timeout: 268 seconds]
jcea has joined #pypy
jcea1 has joined #pypy
jcea1 has quit [Client Quit]
jcea has quit [Ping timeout: 268 seconds]
jcea has joined #pypy
<arigato> @cfbolz: OK
<cfbolz> arigato: I plan to just push like I always have, for not too complicated things
<arigato> OK
<cfbolz> The main difference will be that we'll have a bit more immediate feedback, because we have set up a CI job that runs on every push
<cfbolz> arigato: right now it's minimal, runs only translation. We/I plan to add do that though
<arigato> so the main difference is that we're ruining some cloud machines instead of one of our own
<Dejan> better to ruin cloud machine than own
<cfbolz> arigato: we'll do both
<Dejan> :D
<arigato> :-)
<cfbolz> The buildbots will keep running
<cfbolz> But if they ever break or we won't have people that want to maintain them anymore, we'll still have the github CI jobs
<cfbolz> arigato: cpython does the same dual thing, fwiw
habnabit_ has quit [Ping timeout: 268 seconds]
Dejan has quit [Quit: Leaving]
epony has quit [Remote host closed the connection]
epony has joined #pypy