-
Notifications
You must be signed in to change notification settings - Fork 442
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
parse_date() "ParseError: No numbers were found in input" Python 3.6 and newer #1032
Comments
Can you share what the input ( FWIW, I think this is more a change between babel-2.9.1 and babel-2.11.0 than related to Python versions :) |
hi @akx as far as I can tell the input is from nose unit tests in Sorry, I struggle running tests like this on local and working through debugging so I'm a bit blind to some things in python which I'm used to doing in C++. I agree that it's something that changed between babel-2.9.1 and babel-2.11.0 |
Overview Description
A traceback happens due to a parsing error in babel parse_date() if the input is string. This is inconsistent with older versions of python 3.5 and older work as expected
Steps to Reproduce
I'm not sure how to describe the replication of this issue, but please see the following appveyor build
https://ci.appveyor.com/project/j4321/tkcalendar/builds/48195627
Actual Results
Expected Results
date parsed from string input
Reproducibility
Additional Information
CI testing in Appveyor Visual Studio 2022 image
py3.6 => Babel 2.11.0
py3.7 => Babel 2.13.0
py3.8 => Babel 2.13.0
py3.9 => Babel 2.13.0
py3.10 => Babel 2.13.0
py3.11 => Babel 2.13.0
The text was updated successfully, but these errors were encountered: