Skip to content

Issues: r1chardj0n3s/parse

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.

Sign up for GitHub

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

20 Open 91 Closed
20 Open 91 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Parsing datetime information across several formats
#197 opened Nov 21, 2024 by observingClouds
1
Timestamp can be stored differently than parsed
#162 opened Oct 14, 2023 by gogobera
Floating point with zero digits after the comma
#159 opened Aug 14, 2023 by tovrstra
Length specification is not properly handled with 'x' format character
#149 opened Feb 5, 2023 by crosser
1
Add documentation for usage of "extra_types" good-for-beginner
#148 opened Nov 26, 2022 by ollie-bell
3
Match parameter that is between { and } braces in source string
#146 opened Aug 2, 2022 by samthesuperhero
1
parse.parse("{c:02d}","100") is None
#142 opened Apr 8, 2022 by martinResearch
3
No empty {} placeholders
#138 opened Nov 16, 2021 by dejudicibus
1
Add support for hex in uppercase
#137 opened Aug 17, 2021 by Autopilot9369
Match on empty string
#136 opened Jul 2, 2021 by SeanHayes
2
{:d} parsing ' 0' is wrong
#133 opened Feb 24, 2021 by chengdi1988
1
Use minimum width for zero-padded integer format specifications? wishlist
#131 opened Jan 6, 2021 by azjps
2
explicit string format as {name_:s} does not work bug
#116 opened Aug 13, 2020 by martinResearch 2.0
5
Numbers with a fixed field width/precision are not parsed properly bug
#107 opened Mar 8, 2020 by rgeorgiev583
1
Consider adding Result.span
#101 opened Feb 10, 2020 by florisla
1
Width and precision restrictions are not captured exactly the same as format() generates in some situations bug
#99 opened Dec 23, 2019 by purpleskyfall
1
Way to fall back on default parsing behavior for an overridden type spec wishlist
#49 opened Jun 12, 2017 by Ricyteach
2
Type converter signature should be changed (or extended)
#19 opened Oct 27, 2013 by jenisys
1
Allow a field in the parse format to be optional wishlist
#13 opened Dec 3, 2012 by r1chardj0n3s
7
Add international support for days/months
#1 opened Nov 21, 2011 by r1chardj0n3s
1
ProTip! Type g i on any issue or pull request to go back to the issue listing page.