Adding 'FutureFeature' keyword to avoid rawhide rebase.

When updating, please split out the doc into a subpackage, currently the docs need 93% of the whole package!!

Splitting the docs into a subpackage is expecially usefull for people with a low internet connection...

Thanks!

Anything stopping the update? 

I need pyparsing 1.5.5 for puddletag (bug #645277 ).

1.5.5 has support for python3 which should be included too. 
Updated package in F14 would be nice too.

(In reply to comment #3)
> Anything stopping the update? 
> 
> I need pyparsing 1.5.5 for puddletag (bug #645277 ).
> 
> 1.5.5 has support for python3 which should be included too. 
> Updated package in F14 would be nice too.

How about applying for co-maintainer? ;)

I done some work on the package:

- 1.5.5
- use buildroot macro
- fix wrong file end of line encoding
- convert files to utf-8
- doc subpackage
- python3 subpackage
- rpmlint clean

My work is available here:

spec: http://terjeros.fedorapeople.org/pyparsing/pyparsing.spec
srpm: http://terjeros.fedorapeople.org/pyparsing/pyparsing-1.5.5-1.fc13.src.rpm
koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=2547273


Would be nice with some feedback from Jose.

I was convinced (wrongly as it can be seen) that I had updated pyparsing.
At the moment I am quite busy so could you please drive this release?

Please go ahead for rawhide and F-14.

FWIW your changes to the spec file are sane. :-)

Update coming soon.

pyparsing-1.5.5-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/pyparsing-1.5.5-1.fc14

pyparsing-1.5.5-1.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update pyparsing'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/pyparsing-1.5.5-1.fc14

pyparsing-1.5.5-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.