Popular recipes tagged "parse" but not "datetime"

parse png image (Python)

2013-05-27T22:02:07-07:00

Python recipe 578534 by judy (height, image, parse, png, width).

parse png image find all chunks width height

Python code clone detector (Don't Repeat Yourself) (Python)

2012-07-12T14:59:11-07:00

Python recipe 578206 by fra (analysis, clone, code, dry, duplication, parse, similarity, static, syntax). Revision 2.

Find duplicate code in Python 2/3 source files. Write a nice report about it.

Works at the Abstract Syntax Tree level, which is a robust way to detect clones. See this code duplicated in the Python 3.2 standard library.

Update: I cleaned the code a little bit, made it Python 2.7 compatible and faster.

Parse profile (Python)

2012-10-12T23:40:55-07:00

Python recipe 578280 by Jason Friedman (parse, profile, shell). Revision 3.

export VAR1=foo
export VAR2=bar
export VAR3=$VAR1$VAR2
export VAR4=${VAR1}$VAR2
  export VAR5=${VAR1}indent
export VAR6="text${VAR1} " # With embedded spaces and a comment
export VAR7='${VAR4}' # Leave text within tics as-is

will be read as:

{'VAR1': 'foo',
 'VAR2': 'bar',
 'VAR3': 'foobar',
 'VAR4': 'foobar',
 'VAR5': 'fooindent',
 'VAR6': 'textfoo ',
 'VAR7': '${VAR4}'}

Cheap-date trick; a different way to parse (Python)

2012-03-06T14:08:10-08:00

Python recipe 578064 by Scott S-Allen (cheap, date, format, grep, parse, regex, sharp).

... a light meal with a heavy dose of "tutorial mash" on the side.

In the constructive spirit of "more ways to solve a problem"; this is a portion of my lateral, occasionally oblique, solutions. Nothing new in le régime de grande, but hopefully the conceptual essence will amuse.

Initially started as a response to recipe 577135 which parses incremental date fragments and preserves micro-seconds where available. That script does more work than this, for sure, but requires special flow-control and iterates a potentially incumbering shopping list (multi-dimensional with some detail).

So here's a different box for others to play with. Upside-down in a sense, it doesn't hunt for anything but a numerical "pulse"; sequences of digits punctuated by other 'stuff' we don't much care about.

Missing a lot of things, intentionally, this snippet provides several examples demoin' flexibility. Easy to button-up, redecorate and extend later for show, till then the delightful commentary makes it hard enough to see bones already -- all six lines or so!

Note: The core script is repeated for illustrative purposes. The first is step-by-step, the second is lean and condensed for utilitarian purposes. It is the second, shorter, version that I yanked from a file and gussied up.

Javascript - JSON Parser (only for study) (JavaScript)

2010-07-27T19:36:50-07:00

JavaScript recipe 577337 by Danillo Souza (json, parse).

JSON parser for any object in the script.

OBS: Need a way to identify methods.

Simple regex engine, elementary Python (Python)

2010-07-10T10:43:30-07:00

Python recipe 577251 by Joost Behrends (cached, parse, parsing, recursion, regular_expressions). Revision 40.

A short engine for testing against a regex, understanding the 3 common quantifiers ?,+,* (non-greedy) working on characters, ., [...], [^...], \s, \S, bracketed patterns and group designators \N. Accepts unicode objects and fixed-width encoded strings (but problems with eventual comparisons of trailing bytes in multi-byte utf-letters). Captures up to 10 groups ( (?:...) implemented), which can be used for back referencing and in xreplace(). Captured groups are accessible after the search in the global list xGroups. | is supported, but only in groups and needing nested=True. nested=False is making '(' and ')' common letters.

This is not about Python or for Python, there it has little use beside re. But regarding that re needs about 6,000 lines you might agree with the author, that these 176 lines are powerful. This was the reason to publish it as a recipe - as a kind of (fairly complete) minimal example of a regex tester and as an example for corresponding recursive structures in data (TokenListCache) and code.

Working on this improved the author's understanding of regular expressions - especially of their eventual "greed". "Greedy" quantifiers are a concept, which has to be explained seperately and is coming unexpected: Whoever is scanning a text for '<.*>', s/he will search SGML tags, not the whole text. Even with the star's "greediness" the code has to take care, that '.*' doesn't eat the whole text finding no match for '<.*>' at all. Thus the standard syntax with greedy quantifiers cannot be simpler to implement than this with its mere 3 lines 101, 111 and 121 preventing any greed. Perhaps it is faster - otherwise it is difficult to understand, why the concept "greed" is existing at all.

This engine might be useful here and then under circumstances with nothing else available. Its brevity eases translation to other languages and it can work with arbitrary characters for STAR or PERHAPS (for example).

extract table into 2-vector from html page (Python)

2008-09-03T22:22:42-07:00

Python recipe 576485 by devdoer (html, parse, regex).

extract table into 2-vector from html page

transform a text to another by regex (Python)

2008-09-02T20:30:53-07:00

Python recipe 576481 by devdoer (parse, regex).

transform a text to another by regex