-
Notifications
You must be signed in to change notification settings - Fork 431
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
Test python interpreters without symbols in CI #719
Comments
To continue the discussion from #718,
|
thanks @zanieb ! I just tested out uv quick for the first (and btw, uv is pretty slick on first impressions - I see why I've been hearing so much about it) - and I think that we're still seeing a _PyRuntime symbol , its just coming from the libpython.so rather than the main python executable (like python is compiled with
|
Alas. Well, good to know the distributions are compatible with a profiler even though we strip them, but too bad it's not helpful here :) Why aren't the existing Windows tests sufficient if that's where it's usually broken? (Glad to hear you liked uv!) |
The BSS scanning fallback code broke after python 3.10 was released (#716) and we didn't notice since this we don't test this functionality out in CI.
We should add some tests that exercise this functionality as part of CI
The text was updated successfully, but these errors were encountered: