Med-Mastodon

Paul McGuireIf you maintain an open source package, set up a standing search on scholar.google.com for your package name. You'll get gmail notifications of published papers referencing your package.It's truly gratifying to see students and research teams making use of my pyparsing package to parse data sets and DSLs, so they can quickly get past the pesky parser development stage and get on with the business of their actual field of study. <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#google</a> <a href="https://fosstodon.org/tags/oss" class="mention hashtag" rel="nofollow noopener" target="_blank">#oss</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

Paul McGuirePyparsing 3.2.2 cleans up a formerly internal-only utility method make_compressed_re(), and makes it part of the public API. Given a list of strings, it generates a regex to match those strings and only those (so no cheating like ".*").Here are before/after expressions for matching chemical symbols.<a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/regex" class="mention hashtag" rel="nofollow noopener" target="_blank">#regex</a>

Paul McGuire<a href="https://fosstodon.org/tags/Pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pyparsing</a> API going back to version 1.0.0 (2003) has used a camelCase name scheme for its methods and argument names. In versions 3.0-3.1 (Oct 2021-Jun 2023), I added PEP8-compliant snake_case names, while maintaining synonym definitions for the legacy names for backward compatibility.Soon, pyparsing will begin emitting DeprecationWarnings for the legacy names. To ease this transition, the next release 3.2.2 will include a utility to convert in place scripts that use the legacy names. <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>

Paul McGuirePyparsing sightings - recent posts/pages using pyparsing (2/2):- ciscoconfparse parses configuration files for various network devices using pyparsing <a href="https://pypi.org/project/ciscoconfparse2/" rel="nofollow noopener" translate="no" target="_blank">https://pypi.org/project/ciscoconfparse2/</a>- moto is a mocking package for AWS boto API, using pyparsing for an internal infix notation parser <a href="https://github.com/getmoto/moto" rel="nofollow noopener" translate="no" target="_blank">https://github.com/getmoto/moto</a>- Pegasus SaaS application builder uses pyparsing internally <a href="https://docs.saaspegasus.com/" rel="nofollow noopener" translate="no" target="_blank">https://docs.saaspegasus.com/</a>- EasyABC is an editor for the ABC music notation language <a href="https://github.com/jwdj/EasyABC" rel="nofollow noopener" translate="no" target="_blank">https://github.com/jwdj/EasyABC</a><a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>

Paul McGuirePyparsing sightings - some recent posts/pages using pyparsing (1/2):- Pyparsing is embedded as a parsing engine for Juniper Networks Junos PyEZ automation environment for smart devices. <a href="https://www.juniper.net/documentation/us/en/software/junos-pyez/junos-pyez-developer/junos-pyez-developer.pdf" rel="nofollow noopener" translate="no" target="_blank">https://www.juniper.net/documentation/us/en/software/junos-pyez/junos-pyez-developer/junos-pyez-developer.pdf</a>- Pyparsing included in the examples for the Python Packaging User Guide. <a href="https://packaging.python.org/en/latest/guides/licensing-examples-and-user-scenarios/" rel="nofollow noopener" translate="no" target="_blank">https://packaging.python.org/en/latest/guides/licensing-examples-and-user-scenarios/</a>- Papercrawler uses pyparsing to extract metadata from published papers, journals, and conference proceedings. <a href="https://github.com/sucv/paperCrawler" rel="nofollow noopener" translate="no" target="_blank">https://github.com/sucv/paperCrawler</a><a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/parsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#parsing</a>

Paul McGuireI just released pyparsing 3.2.1 with a very cool addition to the railroad diagrams that pyparsing generates for its parsers - non-terminal diagram elements now link to their definitions elsewhere in the diagram! This is pretty handy when the diagram is for a complex parser, as in this demo of a parser/evaluator for time references like "3 weeks from today" or "0800 two days from now" or "in exactly twenty-four hours". <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/parser" class="mention hashtag" rel="nofollow noopener" target="_blank">#parser</a> <a href="https://fosstodon.org/tags/railroaddiagram" class="mention hashtag" rel="nofollow noopener" target="_blank">#railroaddiagram</a>

Paul McGuireI'm seeing a number of responses from pyparsing users (or matplotlib users) that they are getting a version of pyparsing that is not compatible with their version of Python (they are running Python 3.8 or older, but the new pyparsing release requires Python 3.9 or later). After some experimenting, I found this `requirements.txt` to help in selecting the right pyparsing version:matplotlib pyparsing>=3.2;python_version>="3.9" pyparsing>=3.1;python_version<"3.9"<a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/matplotlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#matplotlib</a>

Paul McGuireAttention <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> users: I just pushed release 3.2.0b3, which will be the last beta before I push out 3.2.0. This includes:- POSSIBLE BREAKING CHANGE: Fixed bug in `transform_string()` where whitespace in the input string was not properly preserved in the output string.- `mypy` type checking is now run as part of pyparsing's CI.- Exception message format can now be customized, by overriding `ParseBaseException.format_message`.Full release notes here: <a href="https://github.com/pyparsing/pyparsing" rel="nofollow noopener" translate="no" target="_blank">https://github.com/pyparsing/pyparsing</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>

Paul McGuireAttention pyparsing users: I just pushed release 3.2.0b1 which mostly just drops support for Python 3.6-3.8, but also changes some exception messages. Please give this release a try before I push the final release in early October.Also includes: - some nice enhancements to mongodb_query_expression.py - a parser for the Lox language defined in Robert Nystrom's "Crafting Interpreters"Full release notes here: <a href="https://github.com/pyparsing/pyparsing/releases/tag/3.2.0b1" rel="nofollow noopener" translate="no" target="_blank">https://github.com/pyparsing/pyparsing/releases/tag/3.2.0b1</a><a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/mongodb" class="mention hashtag" rel="nofollow noopener" target="_blank">#mongodb</a> <a href="https://fosstodon.org/tags/pymongo" class="mention hashtag" rel="nofollow noopener" target="_blank">#pymongo</a> <a href="https://fosstodon.org/tags/craftinginterpreters" class="mention hashtag" rel="nofollow noopener" target="_blank">#craftinginterpreters</a>

Paul McGuireRefreshing my MongoDB skills this week, and I remember thinking it would be nice to have a converter for query expressions, to transform normal infix notation into the nested dict used by the `collection.find()` function. So here is the output of a pyparsing program to do that. See the before/after examples below. The script is included in the pyparsing examples directory at <a href="https://github.com/pyparsing/pyparsing/blob/master/examples/mongodb_query_expression.py" rel="nofollow noopener" translate="no" target="_blank">https://github.com/pyparsing/pyparsing/blob/master/examples/mongodb_query_expression.py</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/mongodb" class="mention hashtag" rel="nofollow noopener" target="_blank">#mongodb</a>

Paul McGuireJust to report that my 3 open source packages pyparsing, littletable, and logmerger (and by extension, textual, which is used by logmerger) all run successfully on Python 3.13b2 (default build) <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/python313" class="mention hashtag" rel="nofollow noopener" target="_blank">#python313</a> <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/littletable" class="mention hashtag" rel="nofollow noopener" target="_blank">#littletable</a> <a href="https://fosstodon.org/tags/logmerger" class="mention hashtag" rel="nofollow noopener" target="_blank">#logmerger</a> <a href="https://fosstodon.org/tags/textual" class="mention hashtag" rel="nofollow noopener" target="_blank">#textual</a>

Paul McGuireGot an issue submitted for pyparsing this week, and it retraces some steps I've written up before. So I put together another pyparsing blog post, walking through this common pitfall for pyparsing beginners: <a href="https://thingspython.wordpress.com/2024/06/01/repetition-in-pyparsing-why-is-it-so-dumb/" rel="nofollow noopener" translate="no" target="_blank">https://thingspython.wordpress.com/2024/06/01/repetition-in-pyparsing-why-is-it-so-dumb/</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/parsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#parsing</a>

Paul McGuireAnd, the 1000th pyparsing question was just posted on SO, and it's a nice one! Plus, it was answered by 31-rep user aRTy! (with only a slight bug in their answer, but they had the right idea) <a href="https://stackoverflow.com/questions/78430312/how-to-get-pyparsing-to-match-1-day-or-2-days-but-fail-1-days-and-2-day" rel="nofollow noopener" translate="no" target="_blank">https://stackoverflow.com/questions/78430312/how-to-get-pyparsing-to-match-1-day-or-2-days-but-fail-1-days-and-2-day</a> <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>

Paul McGuireI just released version 3.1.0 of <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a>. Compatibility with Python 3.12 and the latest version of railroad-diagrams. Many bugfixes and new features, all the details are here: <a href="https://github.com/pyparsing/pyparsing/releases/tag/3.1.0" rel="nofollow noopener" target="_blank">https://github.com/pyparsing/pyparsing/releases/tag/3.1.0</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>

Paul McGuireI just pushed release 3.1.0b1 of pyparsing. 3.1.0 will include support for python 3.12, and will be the last release to support 3.6 and 3.7. If your project uses pyparsing, *please* download this beta release (using "pip install -U pyparsing==3.1.0b1") and open any compatibility issues you might have at the pyparsing GitHub repo (<a href="https://github.com/pyparsing/pyparsing" rel="nofollow noopener" target="_blank">https://github.com/pyparsing/pyparsing</a>). <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>

Paul McGuireAaaaaand... it's out! Pyparsing 3.1.0a1 pre-release available for testing. As easy as firing up a new virtual environment and then `pip install pyparsing==3.1.0a1`! <a href="https://fosstodon.org/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/parsers" class="mention hashtag" rel="nofollow noopener" target="_blank">#parsers</a>

radicalbitsI've been fiddling around with pyparsing for sometime now trying to parse some simple things and I have to give up. The API is a bit confusing for me and I just don't understand the railroad diagrams that it generates. <a href="https://hachyderm.io/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://hachyderm.io/tags/pyparsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyparsing</a>

Recent searches

Search options

Administered by:

Server stats:

#pyparsing