-
Notifications
You must be signed in to change notification settings - Fork 54
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
Please release new version to pypi (python 3.10 issue) #240
Comments
looks like one of the endless issues resulting from the lack of / changing nature of a stable Python ABI :( |
it might be as simple as using |
Moving to cibuildwheel #241 would make releasing a new version less painful. Help welcome. |
We would like to push a new release of Crossbar.io, and this is the only issue we are left crossbario/crossbar#1917 (comment) I would like to avoid removing vmprof (making it optional or what ..) ... is there any chance for a new vmprof release now? |
I think I might have time to look at it later this week |
With the latest vmprof release 0.4.15 and python3.10 we run into: vmprof/vmprof-python#240 Signed-off-by: Bastian Krause <bst@pengutronix.de>
With the latest vmprof release 0.4.15 and python3.10 we run into: vmprof/vmprof-python#240 Signed-off-by: Bastian Krause <bst@pengutronix.de>
With the latest vmprof release 0.4.15 and python3.10 we run into: vmprof/vmprof-python#240 Signed-off-by: Bastian Krause <bst@pengutronix.de>
I have the same issue on Python3.8
|
With the latest vmprof release 0.4.15 and python3.10 we run into: vmprof/vmprof-python#240 Signed-off-by: Bastian Krause <bst@pengutronix.de>
With the latest vmprof release 0.4.15 and python3.10 we run into: vmprof/vmprof-python#240 Signed-off-by: Bastian Krause <bst@pengutronix.de>
Since vmprof has trouble releasing a python 3.10 capable version [1] and it is only needed for profiling in crossbar, make it a soft dependency. All occurrences of vmprof in actual code are already guarded by try except constructs around imports and `_HAS_VMPROF` checks around vmprof use. So it should be safe to drop vmprof from the various reqirements/setup/Makefile files as well as corresponding licensing files. [1] vmprof/vmprof-python#240 Signed-off-by: Bastian Krause <bst@pengutronix.de>
Since vmprof has trouble releasing a python 3.10 capable version [1] and it is only needed for profiling in crossbar, make it a soft dependency. All occurrences of vmprof in actual code are already guarded by try except constructs around imports and `_HAS_VMPROF` checks around vmprof use. So it should be safe to drop vmprof from the various reqirements/setup/Makefile files as well as corresponding licensing files. [1] vmprof/vmprof-python#240 Signed-off-by: Bastian Krause <bst@pengutronix.de>
Since vmprof has trouble releasing a python 3.10 capable version [1] and it is only needed for profiling in crossbar, make it a soft dependency. All occurrences of vmprof in actual code are already guarded by try except constructs around imports and `_HAS_VMPROF` checks around vmprof use. So it should be safe to drop vmprof from the various reqirements/setup/Makefile files as well as corresponding licensing files. [1] vmprof/vmprof-python#240 Signed-off-by: Bastian Krause <bst@pengutronix.de>
Issue persists on Ubuntu 22. This is my first attempt at using vmprof; I'm wondering if I'm looking at the wrong tool? |
Hi Godmar. Vmprof is not the right way to look at the assembly code - PYPYLOG is. |
Thank you for the reply. What exactly is I already used the Could you provide a URL? The only thing I found, beside PS: |
Hi Godmar. Any chance you can join IRC, so we don't have to do it over github issues? There is a bunch of a bit half-assed tools, I personally use jitviewer, but it's not like it's finished. |
I appreciate the offer, but the reason I post here is to help others who may be in the same situation. I also don't use IRC regularly, and wouldn't I need to know a channel name, anyway? |
rgd IRC, yes, it's channel "#pypy" .. |
Well, the problem is that you have a lot of half-working tools (or tools that require some knowledge) that I can explain, but it'll be hard to explain in a non-interactive way. If you want to come up with a documentation out of that, you are more than welcome, but I'm not willing to write full doc on a github issue. |
cpy 3.11 build fails with
|
thanks! fwiw, it makes me feel sad, Python will probably live forever with the consequences of an undefined run-time API (CPyExt). also with the consequences of "broken" dependency management (setuptools/pip). I've again spent hours for the latest crossbar release fiddling with Ethereum Python libraries. well. some things will hunt you, there is no escape;) anyways. |
Version 0.4.17 is now on PyPI with wheels for most x86_64 platforms, including python3.11 |
great news. this is fantastic! thank you for your work - and for vmprof in the first place=) |
The currently released version cannot be install from pypi when using python 3.10. However installation from master branch is possible. Please upload a new release. Below is the log I see when installing frmom pypi
The text was updated successfully, but these errors were encountered: