You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Our company installed the newest Python version lately, namely 3.11. I found that it is not possible for me to install dx:
dx has PyArrow as requirement. PyArrow does currently not support Python 3.11 in its latest stable version (but within its nightly build, to be installed with pip install --extra-index-url https://pypi.fury.io/arrow-nightlies/ --prefer-binary --pre pyarrow). Therefore, I installed the pre-release version (which supports 3.11) in the hope to get dx installed, but discovered that dx has an upper bound for the version of pyarrow (the pyarrow<9.0.0 part in the following output listing) as requirement.
C:\Users\peter.jung>pip install dx --upgrade
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: dx in c:\users\peter.jung\appdata\roaming\python\python311\site-packages (0.1.22)
Collecting dx
Downloading dx-1.2.0-py3-none-any.whl (34 kB)
Collecting SQLAlchemy<2.0.0,>=1.4.40
Downloading SQLAlchemy-1.4.45-cp311-cp311-win_amd64.whl (1.6 MB)
---------------------------------------- 1.6/1.6 MB 791.0 kB/s eta 0:00:00
Requirement already satisfied: ipython>=7.31.1 in c:\users\peter.jung\appdata\roaming\python\python311\site-packages (from dx) (8.7.0)
Requirement already satisfied: pandas<2.0.0,>=1.3.5 in c:\users\peter.jung\appdata\roaming\python\python311\site-packages (from dx) (1.5.2)
Collecting pyarrow<9.0.0,>=8.0.0
Downloading pyarrow-8.0.0.tar.gz (846 kB)
---------------------------------------- 846.6/846.6 kB 1.5 MB/s eta 0:00:00
Installing build dependencies ... done
(PyArrow 8.0.0 is bad since it gives a "missing cmake" error which was fixed in the nightly build.)
I propose to remove this upper bound and adapt dx to pyarrow's new version. Otherwise, we will always have something like the source code equivalent of a festering wound.
Expected behavior
No problems to install dx on Python 3.11. A necessary (and sufficient) condition would be to remove the upper bound for pyarrow's version.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS: Windows
Python Version: 3.11
Library Version: 1.2.0
The text was updated successfully, but these errors were encountered:
Out of curiosity, what's your use case here? Typically dx doesn't do much outside of the Noteable app, so I'm curious how you're using dx or if this was a mixup with another package.
That said, I am overdue on pushing the latest dependency updates and functionality to PyPI. We have a couple more things to knock out before that happens, and I can update here once that's done so you can give it a try.
Describe the bug
Our company installed the newest Python version lately, namely 3.11. I found that it is not possible for me to install dx:
dx has PyArrow as requirement. PyArrow does currently not support Python 3.11 in its latest stable version (but within its nightly build, to be installed with
pip install --extra-index-url https://pypi.fury.io/arrow-nightlies/ --prefer-binary --pre pyarrow
). Therefore, I installed the pre-release version (which supports 3.11) in the hope to get dx installed, but discovered that dx has an upper bound for the version of pyarrow (thepyarrow<9.0.0
part in the following output listing) as requirement.(PyArrow 8.0.0 is bad since it gives a "missing cmake" error which was fixed in the nightly build.)
I propose to remove this upper bound and adapt dx to pyarrow's new version. Otherwise, we will always have something like the source code equivalent of a festering wound.
Expected behavior
No problems to install dx on Python 3.11. A necessary (and sufficient) condition would be to remove the upper bound for pyarrow's version.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: