Bug 1311523 - python-django-debug-toolbar: Provide a Python 3 subpackage
python-django-debug-toolbar: Provide a Python 3 subpackage
Product: Fedora
Classification: Fedora
Component: python-django-debug-toolbar (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Runge
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-02-24 07:11 EST by Tomas Orsava
Modified: 2016-05-21 10:00 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-05-21 10:00:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tomas Orsava 2016-02-24 07:11:17 EST
Upstream, this software supports Python 3. Please provide a Python 3
package for Fedora.

According to the Python packaging guidelines [0], software must be
packaged for Python 3 if upstream supports it.
The guidelines give detailed information on how to do this, and even
provide an example spec file [1].

The current best practice is to provide subpackages for the two Python
versions (called "Common SRPM" in the guidelines). Alternatively, if
nothing depends on your Python2 package, you can just switch to Python 3

It's fine to do this in Rawhide only.

If anything is unclear, or if you need any kind of assistance with the
porting, you can ask on IRC (#fedora-python on Freenode), or reply here.
We'll be happy to help!

[0] https://fedoraproject.org/wiki/Packaging:Python
[1] https://fedoraproject.org/wiki/Packaging:Python#Example_common_spec_file
Comment 1 Dominika Krejčí 2016-05-04 08:35:19 EDT
Hello Matthias,

Do you need any help adding Python 3 support to the RPM?

If you need more instructions, a [guide] for porting Python-based RPMs is available.

[guide] http://python-rpm-porting.readthedocs.org/en/latest/index.html
Comment 2 Matthias Runge 2016-05-04 08:39:19 EDT
You mean, something like time? Feel free to submit a patch.
Comment 3 Tomas Orsava 2016-05-06 08:07:21 EDT
Matthias, when looking at the spec file it seems there already IS a Python 3 support, it's just turned off:

%global with_python3 0

Is there some reason for this? The changelog only mentions that Python 3 support was added.

Thank you for your time.
Comment 4 Matthias Runge 2016-05-09 02:12:12 EDT
Besides tests don't seem to work with python3, there is a build error thrown, something like a typo, but unfortunately I wasn't able to spot it.

Feel free to jump in.
Comment 5 Tomas Orsava 2016-05-09 06:04:45 EDT
A typo in the upstream build process? Or in the specfile?
Comment 6 Matthias Runge 2016-05-09 06:19:22 EDT
must be in the spec file.

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