Skip to content
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

Python 3.12 JPype1 installation error #53

Closed
LewisSarcasm opened this issue Nov 12, 2023 · 2 comments · Fixed by #71
Closed

Python 3.12 JPype1 installation error #53

LewisSarcasm opened this issue Nov 12, 2023 · 2 comments · Fixed by #71

Comments

@LewisSarcasm
Copy link

There is an issue with python 3.12 not correctly installing Ghidriff.

The issue lies with JPype1 not being correctly installed using PIP.

Changing to python 3.10 works for. Perhaps add this into the README section, that the user should not use python 3.12 (maybe 3.11 too).

Within the setup.cfg file there is no mention of any version above 3.10:

classifiers =
    Development Status :: 3 - Alpha
    Intended Audience :: Developers
    License :: OSI Approved :: GNU General Public License v3 (GPLv3)
    Programming Language :: Python :: 3
    Programming Language :: Python :: 3.7
    Programming Language :: Python :: 3.8
    Programming Language :: Python :: 3.9
    Programming Language :: Python :: 3.10
@clearbluejar
Copy link
Owner

Ah thanks for that. Yeah there are recent build issues with jpype on Python 3.12. I have even updated my automated testing until the fix is in.

b9b17db#diff-24ad71c8613ddcf6fd23818cb3bb477a1fb6d83af4550b0bad43099813088686

I will update the setup.cfg to include up to 3.11 for now, until the 3.12 jpype issue is solved.

I will keep this ticket open until the jpype fix is in.

@clearbluejar
Copy link
Owner

Some awesome progress has been made here: jpype-project/jpype#1162 . I will push a new version to support 3.12 when available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants