You can find the details about that package in its review request.

• What is the reason for the Python 2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?)
• What are the upstream/community plans/timelines regarding Python 3?
• What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?)
• Is it an exception for buildtime only or runtime?
• Are there any other packages (incl. setuptools etc.) you need beside the Python interpreter?
• What is the impact on Fedora users if we don't approve this? Will they be able to get the app via other means? Will they leave to another distribution... ?

@besser82 please provide answers. Thanks!

What is the reason for the Python 2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?)

We need it during buildtime to determine the actual Python2 interpreter. During runtime the Python2 interpreter is used to cross-compile and/or cross-test some packages using ptxdist. Besides that the scripts shipped with ptx dist are already working with Python3.

What are the upstream/community plans/timelines regarding Python 3?

Upstream is planning to ditch Python2 before it will be EOL. I'm currently working with upstream to determine wihich steps need to taken.

What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?)

I can help upstream porting the things, that for some reason (a missing patch to a package or minor tweaks) still require Python2 to use Python3 instead.

Is it an exception for buildtime only or runtime?

Both.

Are there any other packages (incl. setuptools etc.) you need beside the Python interpreter?

The Python2 distutils is needed.

What is the impact on Fedora users if we don't approve this?

I don't see to much impact, as the package has not been in Fedora before.

Will they be able to get the app via other means?

Installing from tarball would be an alternative.

Upstream is planning to ditch Python 2 before it will be EOL.

That's in couple months. Can the package just wait for that?

Given the above information, I'm -1. If it's expected to be converted to Python 3 in the near future, let's wait to include it in Fedora proper. @besser82 Can you use COPR in the meantime to prep the packaging?

Consider me -1 as well.

Tagging with meeting because of the negative votes.

We've talked about this on today's meeting:

AGREED: Wait for one more week, deny if no answer from besser82 (+7, 0, -0) (ignatenkobrain, 15:10:53)

@besser82 could you reply please to @sgallagh and @churchyard questions?

Well, I think I can build the package in a COPR until the conversion to Python3 has happened.

OK, let's close this then. The sentiment was clearly negative, and the alternative is viable.