| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
#207); deleted duplicated examples (commit *all* changes this time)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The pyupgrade project is available at
https://github.com/asottile/pyupgrade and can be installed through pip.
The pyupgrade tool automatically upgrades syntax for newer versions of
the language. As pyparsing is now Python 3 only, can apply some cleanups
and simplifications. Ran the tool using the following command:
$ find . -name \*.py -exec pyupgrade --py3-plus {} \;
For now, pyparsing.py was skipped while it is refactored to a package.
|
| |
|
|
| |
pyparsing_common as ppc and pyparsing_unicode as ppu
|
| |
|
|
| |
pyparsing features
|
| |
|
|
|
|
| |
Many editors clean up trailing white space on save. By removing it all
in one go, it helps keep future diffs cleaner by avoiding spurious white
space changes on unrelated lines.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The all caps "UTF-8" causes warnings or errors in some editors. "utf-8"
is more widely recognized. For example, when opening files in Emacs, I
see:
> Warning (mule): Invalid coding system ‘UTF-8’ is specified
> for the current buffer/file by the :coding tag.
> It is highly recommended to fix it before writing to a file.
> Really proceed with writing? (yes or no)
I'm then promped before saving.
The CPython source code uses the lowecase form.
|
| |
|
