parse() is the opposite of format()
Project description
Parse strings using a specification based on the Python format() syntax.
parse() is the opposite of format()
The Format String Syntax is supported with anonymous (fixed-position), named and formatted fields:
{[field name]:[format spec]}
Field names must be a single Python identifier word. No attributes or element indexes are supported (as they would make no sense.)
Numbered fields are also not supported: the result of parsing will include the parsed fields in the order they are parsed.
The conversion of fields to types other than strings is not yet supported.
Some simple parse() format string examples:
>>> parse("Bring me a {}", "Bring me a shrubbery")
<Result ('shrubbery',) {}>
>>> r = parse("The {} who say {}", "The knights who say Ni!")
>>> print r
<Result ('knights', 'Ni!') {}>
>>> print r.fixed
('knights', 'Ni!')
>>> r = parse("Bring out the holy {item}", "Bring out the holy hand grenade")
>>> print r
<Result () {'item': 'hand grenade'}>
>>> print r.named
{'item': 'hand grenade'}
Most of the Format Specification Mini-Language is supported:
[[fill]align][sign][#][0][width][,][.precision][type]
The align operators will cause spaces (or specified fill character) to be stripped from the value. The alignment character “=” is not yet supported.
The comma “,” separator is not yet supported.
The types supported are the not the format() types but rather some of those types b, o, h, x, X and also regular expression character group types d, D, w, W, s, S and not the string format types. The format() types n, f, F, e, E, g and G are not yet supported.
Type |
Characters Matched |
|---|---|
w |
Letters and underscore |
W |
Non-letter and underscore |
s |
Whitespace |
S |
Non-whitespace |
d |
Digits (effectively integer numbers) |
D |
Non-digit |
b |
Binary numbers |
o |
Octal numbers |
h |
Hexadecimal numbers (lower and upper case) |
x |
Lower-case hexadecimal numbers |
X |
Upper-case hexadecimal numbers |
Do remember though that most often a straight type-less {} will suffice where a more complex type specification might have been used.
So, for example, some typed parsing, and None resulting if the typing does not match:
>>> parse('Our {:d} {:w} are...', 'Our 3 weapons are...')
<Result ('3', 'weapons') {}>
>>> parse('Our {:d} {:w} are...', 'Our three weapons are...')
None
And messing about with alignment:
>>> parse('with {:>} herring', 'with a herring')
<Result ('a',) {}>
>>> parse('spam {:^} spam', 'spam lovely spam')
<Result ('lovely',) {}>
Note that the “center” alignment does not test to make sure the value is actually centered. It just strips leading and trailing whitespace.
See also the unit tests at the end of the module for some more examples. Run the tests with “python -m parse”.
Version history (in brief):
1.1.1 documentation improvements
1.1.0 implemented more of the Format Specification Mini-Language and removed the restriction on mixing fixed-position and named fields
1.0.0 initial release
This code is copyright 2011 eKit.com Inc (http://www.ekit.com/) See the end of the source file for the license of use.
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file parse-1.1.1.tar.gz.
File metadata
- Download URL: parse-1.1.1.tar.gz
- Upload date:
- Size: 6.3 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | c383901d5e15b8f3f6c265d1afbb4e8a1011b9611bdf11104a2fdacd5fa9b4e7 |
|
| MD5 | fe655dac7d5e5786acbedad24adb22d0 |
|
| BLAKE2b-256 | d66ae067b870bdf02c1677fcb2a08ced2a77a814824c221e47fc66f43fb9bb9e |
