r1chardj0n3s/parse

Issues

• Still maintained? Want help to maintain parse?

  #154 opened a year ago by nabobalis
  1

• what is the unused match arg in multiple functions?

  #173 opened a year ago by KRRT7
  1

• Search for a certain pattern error at the end of a string

  #182 opened 8 months ago by popu2do
  1

• How do I match in the middle of a string?

  #183 opened 6 months ago by Znunu
  3

• How to get the desired result？

  #186 opened 3 months ago by gitlGl
  2

• Suggestion :u to detect url

  #141 opened 4 months ago by ukgenes
  2

• Cardinality support

  #181 opened 4 months ago by fliiiix
  2

• compile and parse return different results

  #180 opened 8 months ago by osown
  1

• Usage with pandas df.str.extract and .match?

  #177 opened 9 months ago by marfel
  1

• [request]millisecond support

  #127 opened 10 months ago by NaokiSato102
  6

• Found a possible security concern

  #175 opened a year ago by psmoros
  0

• Allow using a Parser as a formatter

  #172 opened a year ago by ymost
  4

• strftime formatting

  #150 opened a year ago by bendichter
  1

• Length specification is not properly handled with 'x' format character

  #149 opened 2 years ago by crosser
  1

• Find all files with matching paths

  #135 opened a year ago by martinResearch
  2

• Add documentation for usage of "extra_types"

  #148 opened 2 years ago by ollie-bell
  3

• A very weird performance problem while parsing

  #163 opened a year ago by mcoulont
  2

• Use patterns inductively doesn't seem to work

  #160 opened a year ago by mcoulont
  1

• Timestamp can be stored differently than parsed

  #162 opened a year ago by gogobera
  0

• Where is located the split between two zones when there is more than one possibility?

  #161 opened a year ago by mcoulont
  2

• Floating point with zero digits after the comma

  #159 opened a year ago by tovrstra
  0

• Hash mismatch when fetching 1.19.0

  #158 opened a year ago by danielhoherd
  3

• Binary hash in pypy changed for release 1.19.0

  #156 opened a year ago by nmacdonald
  7

• Suggestion: in readme put installation section

  #140 opened a year ago by in-tension
  0

• License on pypi

  #145 opened a year ago by klukola
  1

• pip install parse doesn't work

  #143 opened a year ago by superhiro2a
  3

• Possible to publish wheel?

  #144 opened a year ago by mneil
  1

• Move to `pyproject.toml` instead of `setup.py` for packaging

  #147 opened a year ago by gahjelle
  3

• parse.parse("{c:02d}","100") is None

  #142 opened 3 years ago by martinResearch
  3

• Match parameter that is between { and } braces in source string

  #146 opened 2 years ago by samthesuperhero
  1

• No empty {} placeholders

  #138 opened 3 years ago by dejudicibus
  1

• Match on empty string

  #136 opened 3 years ago by SeanHayes
  2

• Add support for hex in uppercase

  #137 opened 3 years ago by Autopilot9369
  0

• {:d} parsing ' 0' is wrong

  #133 opened 4 years ago by chengdi1988
  1

• Center alignment / stripping in 1.17 incompatible with 1.16

  #118 opened 3 years ago by catcaf
  1

• Use minimum width for zero-padded integer format specifications?

  #131 opened 4 years ago by azjps
  2

• Format types are not recognized if using field numbering

  #125 opened 4 years ago by kcbrowning
  0

• explicit string format as {name_:s} does not work

  #116 opened 4 years ago by martinResearch
  5

• accessor for _named_fields

  #114 opened 4 years ago by martinResearch
  5

• Not matching newlines

  #123 opened 4 years ago by giladreti
  0

• Release-admin hint: Tags are missing for released versions

  #120 opened 4 years ago by jenisys
  1

• int_convert: Memory effect regarding number-base if parser is used multiple times

  #121 opened 4 years ago by jenisys
  4

• add dot access interface to `result` object

  #117 opened 4 years ago by wasdee
  3

• seach cut the result with {:^}

  #112 opened 4 years ago by diegomcas
  1

• error when pickling a parser with type conversions

  #110 opened 4 years ago by martinResearch
  0

• [wishlist] Ability to get a set of values in a result

  #108 opened 4 years ago by victorromeo
  2

• Can't parse empty variable

  #109 opened 4 years ago by akhilgargjosh
  1

• Numbers with a fixed field width/precision are not parsed properly

  #107 opened 5 years ago by rgeorgiev583
  1

• Potentially unexpected behaviour with "=" character

  #106 opened 5 years ago by s16h
  3

• Various issues parsing singed or negative numbers

  #102 opened 5 years ago by vladikcomper
  0