Accepting request 357104 from devel:languages:python

1

OBS-URL: https://build.opensuse.org/request/show/357104
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-pyparsing?expand=0&rev=22
This commit is contained in:
Dominique Leuenberger 2016-02-16 08:27:00 +00:00 committed by Git OBS Bridge
commit 5012da3925
4 changed files with 86 additions and 5 deletions

View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:06e729e1cbf5274703b1f47b6135ed8335999d547f9d8cf048b210fb8ebf844f
size 1462653

3
pyparsing-2.0.7.tar.gz Normal file
View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:2ce0db3c70ec0413603d4aea389e4ece34ff93c265649b1c5c7d56e3c2cf19c4
size 1141457

View File

@ -1,3 +1,83 @@
-------------------------------------------------------------------
Mon Feb 1 11:11:39 UTC 2016 - toddrme2178@gmail.com
- update to version 2.0.7:
* Simplified string representation of Forward class, to avoid memory
and performance errors while building ParseException
messages. Thanks, Will McGugan, Andrea Censi, and Martijn Vermaat
for the bug reports and test code.
* Cleaned up additional issues from enhancing the error messages for
Or and MatchFirst, handling Unicode values in expressions. Fixes
Unicode encoding issues in Python 2, thanks to Evan Hubinger for
the bug report.
* Fixed implementation of dir() for ParseResults - was leaving out
all the defined methods and just adding the custom results names.
* Fixed bug in ignore() that was introduced in pyparsing 1.5.3, that
would not accept a string literal as the ignore expression.
* Added new example parseTabularData.py to illustrate parsing of
data formatted in columns, with detection of empty cells.
* Updated a number of examples to more current Python and pyparsing
forms.
- update to version 2.0.6:
* Fixed a bug in Each when multiple Optional elements are present.
Thanks for reporting this, whereswalden on SO.
* Fixed another bug in Each, when Optional elements have results
names or parse actions, reported by Max Rothman - thank you, Max!
* Added optional parseAll argument to runTests, whether tests should
require the entire input string to be parsed or not (similar to
parseAll argument to parseString). Plus a little neaten-up of the
output on Python 2 (no stray ()'s).
* Modified exception messages from MatchFirst and Or
expressions. These were formerly misleading as they would only
give the first or longest exception mismatch error message. Now
the error message includes all the alternatives that were possible
matches. Originally proposed by a pyparsing user, but I've lost
the email thread - finally figured out a fairly clean way to do
this.
* Fixed a bug in Or, when a parse action on an alternative raises an
exception, other potentially matching alternatives were not always
tried. Reported by TheVeryOmni on the pyparsing wiki, thanks!
* Fixed a bug to dump() introduced in 2.0.4, where list values were
shown in duplicate.
- update to version 2.0.5:
* (&$(@#&$(@!!!! Some "print" statements snuck into pyparsing
v2.0.4, breaking Python 3 compatibility! Fixed. Reported by
jenshn, thanks!
- changes from Version 2.0.4:
* Added ParserElement.addCondition, to simplify adding parse actions
that act primarily as filters. If the given condition evaluates
False, pyparsing will raise a ParseException. The condition should
be a method with the same method signature as a parse action, but
should return a boolean. Suggested by Victor Porton, nice idea
Victor, thanks!
* Slight mod to srange to accept unicode literals for the input
string, such as "[а-яА-Я]" instead of
"[\u0430-\u044f\u0410-\u042f]". Thanks to Alexandr Suchkov for the
patch!
* Enhanced implementation of replaceWith.
* Fixed enhanced ParseResults.dump() method when the results
consists only of an unnamed array of sub-structure
results. Reported by Robin Siebler, thanks for your patience and
persistence, Robin!
* Fixed bug in fourFn.py example code, where pi and e were defined
using CaselessLiteral instead of CaselessKeyword. This was not a
problem until adding a new function 'exp', and the leading 'e' of
'exp' was accidentally parsed as the mathematical constant
'e'. Nice catch, Tom Grydeland - thanks!
* Adopt new-fangled Python features, like decorators and ternary
expressions, per suggestions from Williamzjc - thanks William! (Oh
yeah, I'm not supporting Python 2.3 with this code any more...)
Plus, some additional code fixes/cleanup - thanks again!
* Added ParserElement.runTests, a little test bench for quickly
running an expression against a list of sample input
strings. Basically, I got tired of writing the same test code over
and over, and finally added it as a test point method on
ParserElement.
* Added withClass helper method, a simplified version of
withAttribute for the common but annoying case when defining a
filter on a div's class - made difficult because 'class' is a
Python reserved word.
-------------------------------------------------------------------
Mon May 11 17:40:24 UTC 2015 - benoit.monin@gmx.fr

View File

@ -1,7 +1,7 @@
#
# spec file for package python-pyparsing
#
# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@ -17,7 +17,7 @@
Name: python-pyparsing
Version: 2.0.3
Version: 2.0.7
Release: 0
Url: http://pyparsing.wikispaces.com/
Summary: Grammar Parser Library for Python
@ -26,6 +26,7 @@ Group: Development/Languages/Python
Source: http://pypi.python.org/packages/source/p/pyparsing/pyparsing-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-build
BuildRequires: python-devel
BuildRequires: python-setuptools
Provides: python-parsing = %{version}
Obsoletes: python-parsing < %{version}
%if 0%{?suse_version} && 0%{?suse_version} <= 1110