-
-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyperformance doesn't work on the current Python 3.11 dev version: fail to install greenlet #113
Comments
Any further word on this? I encountered it as well. |
You can hack requirements.txt to not install greenlet, and disable benchmarks using it. Or someone can try to port greenlet to Python 3.11. |
Thanks, I gave that a whirl, but just wind up with an inability to install pyperformance 1.0.3 into the virtual environment later in the process. I think my problem is more basic and reflects a basic unfamiliarity with both virtual environments and how pip searches for packages. This is the eventual error (after removing greenlet from various requirements.txt files): Command /home/skip/src/python/cpython/venv/cpython3.11-387285c4875d-compat-bb6573ba2f42/bin/python -m pip install pyperformance==1.0.3 failed with exit code 1 This kind of makes sense, because pyperformance 1.0.3 only exists in my git checkout. It's not been installed anywhere (most importantly, is not yet available on PyPI). Is there a way to tell the venv construction (or pip) that pyperformance 1.0.3 can be found in ~/src/python/pyperformance? |
|
Yes, that works from my ~/src/python/cpython git checkout (and I did install it exactly that way). How do I instruct the virtual environment construction process (which apparently uses a symlink to my locally compiled python executable) to also look there? Here's what I'm trying to execute:
and here's the tail end of the output showing that pip was unable to find pyperformance 1.0.3:
|
Ah, I misunderstood, if it's the pyperformance command that runs pip, I don't know. Sorry for the noise. |
FYI, I recently merged a change that relates to this. If installing a benchmark's requirements fails then that benchmark is skipped and the other benchmarks still run. You can run against main or wait for the next release (1.1.0?). |
I'm trying to run against cpython main and pyperformance main. I have two sandboxes in sibling directories, cpython and pyperformance. My basic process looks like this:
So far, so good. Then I run (still in my cpython sandbox):
It churns for a bit then spits out the error about not being able to find pyperformance 1.0.3. While writing this it occurred to me that maybe I shouldn't be running from the cpython directory. I tried running from the pyperformance sandbox:
That seems to be churning along much better. Not sure why this didn't occur to me before. |
Take a look at the "compile" command ( |
Nice. I can set it up to performance test two or three versions while I sleep. :-) |
This should fixed once CPython 3.11.0a4 is released and python-greenlet/greenlet#280 is merged. |
The text was updated successfully, but these errors were encountered: