Hello there,
To package some python3-based stuff I need 'msgpack', 'llfuse', 'Cython'
modules built for Python 3.4 which is the current version of Python 3 in
epel7.
Would it be reasonable to file a bug against 'python-msgpack', et al. in
epel7 to adapt the package spec and get 'python34-msgpack' etc. packages,
or there are any objections against that?
Thanks,
--
wbr, Denis.

Hello all,
I recently upstreamed some fixes to a new RPM dependency generator
that will be available as an option for distributions to enable. The
new generator uses python .egg data to generate Provides and Requires
in the form of pythonXegg(Y), where X is the Python major version and
Y is the module.
The code for the new generator is available in RPM's GitHub[1]. I've
also made a package in Copr[2] for members of the Python SIG to test
out and provide feedback.
I would greatly appreciate it if the Python SIG would try it out. It's
available for Fedora 22, 23, and rawhide through the Copr.
There is one issue I haven't quite been able to figure out, though.
When being run using Python 3 (Fedora 23+ default), it appears to add
an unversioned "python(abi)" Require to modules on top of the
versioned one. This does not occur when the code is being run in
Python 2 (Fedora 22 default), and I cannot quite figure out why this
is happening.
If anyone has any idea, please let me know, as I would definitely like
this to fix this issue so that it is perfectly functional on both
Python 2 and Python 3.
The Python interpreter being used can be switched in
/usr/lib/rpm/fileattrs/pythoneggs.attr
Best regards,
Neal
[1]: https://github.com/rpm-software-management/rpm/blob/master/scripts/python...
[2]: https://copr.fedoraproject.org/coprs/ngompa/rpm-depgen-pythoneggs/
--
真実はいつも一つ！/ Always, there's only one truth!

Hello,
matplotilb has tagged version 1.5.0. Is there anything we can do to
expedite getting it into the fedora build system?
This version has a new required dependency, cycler, which is available on
pypi and https://github.com/matplotlib/cycler .
Tom