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

agate requires parsedatetime != 2.5 but won't allow 2.6 #766

Closed
howff opened this issue May 10, 2022 · 3 comments
Closed

agate requires parsedatetime != 2.5 but won't allow 2.6 #766

howff opened this issue May 10, 2022 · 3 comments
Labels

Comments

@howff
Copy link

howff commented May 10, 2022

Trying to install agate (1.6.3) it complains that parsedatetime must be !=2.5 !=2.6 >=2.1 but according to #743 only 2.5 is the problem. Is there some reason why v2.6 is not allowed?

@jpmckinney
Copy link
Member

It doesn't allow it due to bear/parsedatetime#247. I suppose we can relax it now that we dropped Python 2.7.

@jpmckinney jpmckinney added the bug label Dec 20, 2022
@jakeberesford-palmetto
Copy link

It would be great to get this updated as parsedatetime v2.4 depends on future, which appears to be unmaintained and has a CVE PythonCharmers/python-future#610 - that dependency is dropped in parsedatetime v2.5+

Relaxing this version pin will resolve a high-severity CVE in one of my projects.

@jpmckinney
Copy link
Member

2.6 is now allowed in 1.7.1.

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

No branches or pull requests

3 participants