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 | Matti: I made a bit of progress, the tests now only segfault towards the end
Atque has joined #pypy
Atque has quit [Quit: ...]
Atque has joined #pypy
otisolsen70 has joined #pypy
xcm_ has quit [Ping timeout: 244 seconds]
xcm has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
Julian has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
Julian has quit [Quit: leaving]
<Hodgestar> mattip: Woot?
<mattip> any ideas why the hpy-0.0.4 extra_tests/hpy_tests/_vendored/conftest.py is not being picked up?
<mattip> I think the conftest.py one directory up is being pulled in, but not the _vendored one
slav0nic has joined #pypy
slav0nic has quit [Ping timeout: 248 seconds]
slav0nic has joined #pypy
Atque has quit [Remote host closed the connection]
Atque has joined #pypy
<mattip> ahh, it is a limitation in pytest_addoption which must be in the toplevel conftest.py
komasa has joined #pypy
otisolsen70 has quit [Quit: Leaving]
<komasa> I vaguely recall pypy being slower than CPython when run under a debugger (specifically in PyCharm), but I can't rememember what the rough factor of this was. In a related question: Is there some easy way to keep a pypy and a cpython virtual env in sync in terms of installed packages and versions?
jcea has joined #pypy
jcea1 has joined #pypy
jcea has quit [Read error: Connection reset by peer]
jcea1 is now known as jcea
<fijal> tumbleweed: ping?
jcea has quit [Ping timeout: 256 seconds]
<tumbleweed> fijal: ohi (from CPT)
<jean-paul[m]> komasa: nix would be a good way to keep two such environments in sync
<jean-paul[m]> let mkenv = python: python.withPackages(ps: [ ... ]); in { cpy = mkenv pkgs.python3; pypy = mkenv pkgs.pypy3; }
<jean-paul[m]> (wrapped up in the new flake format for convenient cli access)
<komasa> jean-paul[m]: I have various packages in that env that are installed via --editable, and that would just not work with the nix philosophy at all
<jean-paul[m]> I don't know if the tension between "well-specified, carefully-controlled environments" and "ad-hoc mutable environments" is _absolutely_ irreconcilable or merely extremely tricky to navigate.
<jean-paul[m]> I have Nix-managed environments with`--editable`-like setup for single Python packages, though, so I suppose that could probably generalize to multiple Python packages if you tried hard enough, so I guess it's probably not irreconcilable.
<komasa> I'm currently sitting next to a few Nix Maintainers in the hackspace, and they didn't sound convinced that this was a good idea
<jean-paul[m]> The trouble is we're awash in a sea of bad ideas. Is it a worse idea than some tool that carefully juggles a bunch of venvs? I dunno. Maybe, maybe not.
<jean-paul[m]> Just use tox, right? That always works.
<jean-paul[m]> I don't have any better suggestions, anyway.
<komasa> My hope was that maybe there is some trick like a `.pth` file. I think the issue with just that is native code though that has to be built against the interpreter
otisolsen70 has joined #pypy
_whitelogger has joined #pypy
otisolsen70 has quit [Quit: Leaving]
slav0nic has quit [Ping timeout: 244 seconds]
jcea has joined #pypy