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
Broken Python 2.x support in new release 0.11.0 #495
Comments
Yes, this is really bad. I spent the last 3 hours trying to get @platformio up and running again. Turns out, it runs against this error. @ivankravets are you already aware of this issue? I am pretty sure you will get tons of false bug reports, as this causes (yet another) Install Endless Loop in Atom.... |
@GrimmiMeloni I can't reproduce this issue with my default Python 2.7.10 on macOS. What are your OS and Python version? |
And I found why all builds is green... To run tests we need to install deps from
And as we can see
But |
I hope this patch should fix issue:
Tested on my local, everything works fine. |
Same issue #491 |
@Gr1N You are right, this is a CRITICAL issue. @crsmithdev could you make a new release of "arrow" with adding a dependency to Thanks! |
@Gr1N The better is to check Python version and dynamically configure |
Do as you think is right, I just want to get a new package with fix :) |
@GrimmiMeloni temporary fixed as extra deps for @platformio platformio/platformio-core@37a2cce Please remove |
Please check the PR i've created to address this issue, we need to push this asap. |
Fixed on https://pypi.python.org/pypi/arrow/0.12.0 - please upgrade arrow if you're using python 2.x and arrow 0.11.0 |
Thank you! |
Nice one, everybody! HotHotfix 😉 |
still have the issue with 0.12 python 2.7 |
same here. |
For anyone else arriving here, this is resolved in 0.12.1 |
I'm seeing this with 0.12.1 on Debian 8:
|
@rmechler This is strange. Can you try a |
I also see this error w/ arrow 0.12.1 (python 2.7.10 on Mac OS 10.11.6):
|
I am also seeing this issue on 0.12.1 I uninstalled 0.12.1, installed 0.12.0 and it worked fine. |
This issue should not be closed? |
I am running into this issue when installing audreyr/cookiecutter (due to cookiecutter > jinja2-time > arrow). The issue seems to be that pip looks for What does needs fixing here and where does it needs to be fixed? pip install
pip install -v
test import
pip install --user backports.functools_lru_cache==1.2.1
test import with 1.2.1
|
This is still an issue on python 2.6 since the current setup.py require only covers 2.7:
I guess currently in the setup.py file the require is defined as - |
As suggested in arrow-py#495 adds support for Python 2.6 and lower
python2.7下 |
FWIW, I just ran into this error when installing aws-sam-cli, which depends on arrow. In my case, the issue was indeed related to installing in the user scheme. This caused pip to install backports.functools_lru_cache in my home directory site-packages, but I also have backports.configparser installed globally. It seems as if the presence of the 'backports' module in global prevents python from seeing the one in my user directory. This problem seems to be specific to 'backports' for some reason. I was able to temporarily work around the problem by globally installing backports_functools_lru_cache. |
@bgruber that's useful to know, what version of python were you using? |
2.7.15 on ubuntu 18.10. |
Is this issue still occurring for people? I am unable to reproduce this on the latest Here are the dependencies (and their respective versions) that are installed when I run |
If anyone is still having issues, feel free to report it here. For now, we will close this issue as it seems to be an issue with either |
my issue does appear to be resolved on ubuntu 19.04 with python 2.7.16. |
Thanks for letting us know! I think it is worth compiling a list of solutions to try if this issue occurs again for someone in the future:
|
Hi, Details follow: $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
$ pip -V
pip 19.1.1 from /usr/local/lib/python2.7/dist-packages/pip (python 2.7)
$ python -V
Python 2.7.15+
$ pip list | grep arrow
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
arrow 0.14.2
$ pip list | grep back
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
backports.functools-lru-cache 1.5
$ python
Python 2.7.15+ (default, Nov 27 2018, 23:36:35)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import arrow
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python2.7/dist-packages/arrow/__init__.py", line 2, in <module>
from .api import get, now, utcnow
File "/usr/local/lib/python2.7/dist-packages/arrow/api.py", line 10, in <module>
from arrow.factory import ArrowFactory
File "/usr/local/lib/python2.7/dist-packages/arrow/factory.py", line 17, in <module>
from arrow import parser
File "/usr/local/lib/python2.7/dist-packages/arrow/parser.py", line 14, in <module>
from backports.functools_lru_cache import lru_cache # pragma: no cover
ImportError: No module named functools_lru_cache
>>> Has this been RCA-ed as fixed if I upgrade to 2.7.16? As you can see I'm an LTS kind of person - prefer stuff to just work, not keen to diverge from the standard install if I can avoid it. |
@timothycdbarnes thanks for the detailed feedback. Think you can answer a couple of follow up questions for me?
|
I am beginning to suspect that this error may be caused by either |
We have attempted a fix for this in |
hi @jadchaar unfortunately I am faced with the same issue, here are my details:
|
Hi @mkumar118, I recommend removing |
Hi @jadchaar thank you, |
Hello,
New release (0.11.0) is broken for Python 2.x users, below you can find steps to reproduce:
Could you fix this please?
The text was updated successfully, but these errors were encountered: