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
_whitelogger has joined #pypy
jcea has quit [Ping timeout: 276 seconds]
_whitelogger has joined #pypy
itamarst has quit [Quit: Connection closed for inactivity]
AndyAndyBoBandy has joined #pypy
<AndyAndyBoBandy> Hi! I'm not regularly using PyPy, but in CI have a runner for Windows+PyPy3.10. Part of the tests install a dummy pyproject.toml package with the flit_core.buildapi backend. It's supposed to use flit_core >=3.11, but in this runner only seems to see up to 3.10.1. Why wouldn't it see and use newer versions from PyPi? It works ok in the Ubuntu and MacOS PyPy3.10 runners.
AndyAndyBoBandy has quit [Quit: Konversation terminated!]
slav0nic has joined #pypy
slav0nic has quit [Ping timeout: 265 seconds]
slav0nic has joined #pypy
slav0nic has quit [Ping timeout: 276 seconds]
jcea has joined #pypy
jcea has quit [Ping timeout: 248 seconds]
Dejan has joined #pypy
Dejan has quit [Quit: Leaving]
nightstrike has quit [Quit: Connection closed for inactivity]
itamarst has joined #pypy