Bug 950775 - Update python3-pyparsing to 2.0.1
Summary: Update python3-pyparsing to 2.0.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pyparsing
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: José Matos
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 950769 (view as bug list)
Depends On:
Blocks: 916965
TreeView+ depends on / blocked
 
Reported: 2013-04-10 20:49 UTC by Ralph Bean
Modified: 2013-11-14 03:29 UTC (History)
5 users (show)

Fixed In Version: pyparsing-2.0.1-1.fc20
Clone Of:
Environment:
Last Closed: 2013-11-14 03:29:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ralph Bean 2013-04-10 20:49:58 UTC
pyparsing (the py2 package) can remain at 1.5.7, but a special python3 branch of pyparsing has been created at version 2.0.0 as you can see here https://pypi.python.org/pypi/pyparsing

This is needed for other packages like python3-cliff-1.3.2.

Comment 1 Terje Røsten 2013-04-10 21:05:53 UTC
Should we move python3 subpackage into separate package then? 

I did something similar with beautifulsoup.

Comment 2 José Matos 2013-04-18 16:44:51 UTC
One possibility, at least regarding fedora (as opposed in this case to epel) is to release pyparsing 2.0 for Fedora.

pyparsing 2.0 has dropped the support for older versions of python but from what I have seen I expect it to work with python 2.7 that is the current version in all supported versions of Fedora.

FWIW we have discussed the issue of updating pyparsing on #947655

If needed I can submit another version for pyparsing2 but before doing that I would like to consider the best scenario.

While studying the sources I noticed that for example some of the documentation available in 1.5.6 is not present in 1.5.7 but it is again in 2.0. Weird...

Comment 3 José Matos 2013-07-21 06:26:10 UTC
With the latest release of 2.0.1:

https://pypi.python.org/pypi/pyparsing/2.0.1

As far as I can see it works again for python 2 and 3 so the need to split the package in two should be gone.

Comment 4 Thomas Spura 2013-08-07 13:55:53 UTC
*** Bug 950769 has been marked as a duplicate of this bug. ***

Comment 5 Thomas Spura 2013-08-07 13:56:57 UTC
FYI: python3-matplotlib-1.3.0 shows this warning:
/usr/lib64/python3.3/site-packages/matplotlib/mathtext.py:46: UserWarning: Due to a bug in pyparsing <= 2.0.0 on Python 3.x, packrat parsing has been disabled.  Mathtext rendering will be much slower as a result.  Install pyparsing 2.0.0 or later to improve performance.

Comment 6 Fedora End Of Life 2013-09-16 13:28:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 7 Zbigniew Jędrzejewski-Szmek 2013-10-24 15:30:08 UTC
Any progress?

Comment 9 José Matos 2013-11-07 11:53:23 UTC
Please do. And if you consider those fit to stable releases please do it as well.

Recently I got busy with a non-fedora project called David (my new born son) and that is why I have been slow to react on this subject.

Comment 10 Fedora Update System 2013-11-07 20:36:41 UTC
pyparsing-2.0.1-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/pyparsing-2.0.1-1.fc20

Comment 11 Fedora Update System 2013-11-08 18:40:01 UTC
Package pyparsing-2.0.1-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pyparsing-2.0.1-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20950/pyparsing-2.0.1-1.fc20
then log in and leave karma (feedback).

Comment 12 Fedora Update System 2013-11-14 03:29:05 UTC
pyparsing-2.0.1-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.