Package Error: python-dateutil

[weasteam]

Would you please support the newest version of python-dateutil?

ERROR: zappa 0.48.2 has requirement python-dateutil<2.7.0,>=2.6.1, but you'll have python-dateutil 2.8.0 which is incompatible.

[gonwi]

I am running with the same issue here. Also encountered problem with jmespath.

ERROR: zappa 0.48.2 has requirement jmespath==0.9.3, but you'll have jmespath 0.9.4 which is incompatible.
ERROR: zappa 0.48.2 has requirement python-dateutil<2.7.0,>=2.6.1, but you'll have python-dateutil 2.8.0 which is incompatible.

[kittylon]

I also have the same error for jmespath and python-dateutil, any news on this?

[thibaut-pro]

This is impacting us as well.

[jneves]

This is solved by #1998 which I hope to merge and release this week. And we should be done with pinned dependencies altogether.

[brianhelba]

@jneves Ping. Now that #1998 is merged and botocore is not restricted to python-dateutil<2.7.0, can the pinning of python-dateutil in Zappa be removed?

[hickeroar]

This is solved by #1998 which I hope to merge and release this week. And we should be done with pinned dependencies altogether.

This is still an issue. I'm trying to convert an app that has multiple dependencies which require dateutil 2.8+ over to Zappa/Lambda, but I cannot because of this issue. Do we have any kind of ETA for when this will be fixed? I can't deploy the app in a working state, because the Zappa "<2.7.0" requirement forces the shipped version to be less than what I require.

[jneves]

Not yet, haven't found the specific reason why it was locked in the first place. Will have to check if it's just some API change.

[tommie-lie]

I did some digging and found #1449 from times when requirements.txt still contained hard version dependencies. python-dateutil was pinned to 2.6, because botocore at the time still depended on <2.7. botocore has since removed the dependency on python-dateutil completely (c.f. botocore/botocore@7477a82b379b0e5b36e727a32002f554a4862d2e).

I also checked Zappas sourcecode, and dateutil is used only in cli.py to parse ISO timestamps. There are no breaking changes and all tests are still running with dateutil>2.8.

@jneves would you like a PR for loosening python-dateutil version?

[bmyrtil-fsns]

Any update on this? Like everyone else, I am starting to run into issues because of the pinned version.

[amsal-muhammad]

Please update. My dependencies don't resolve due to this.

[jasonrhaas]

FYI there is a PR that is ready to be merged but is just sitting around. I got around this issue but installing zappa directly off that branch. The branch is feature/updates-including-dateutil.

In your virtualenv:

pip uninstall zappa
pip install git+https://github.com/Miserlou/Zappa.git@feature/updates-including-dateutil#egg=zappa
pip install -U python-dateutil

[jneves]

Thanks, will hopefully sort this out tomorrow.

[amsal-muhammad]

Please merge it :(

[JasonSanchez]

Ran into this error today as well.

python-dateutil<2.7.0 (from zappa==0.51.0 python-dateutil>=2.7.3 (from pandas==1.1.1->awswrangler==1.8.1

[jayfid]

Ran into this today too, but I'm unsure if I should wait for the release or attempt a different approach. Is something preventing this from being released?

[nino-finch]

Running into this issue today too :(

[chris-erickson]

Add this instead until we get a real release.

-e git+https://github.com/Miserlou/Zappa.git@0c8d99ddbc297124d93c166652013abba50ee86e#egg=zappa

[louq-gharnati]

Running into this issue today too :(