Bug 1679368

Summary:	Provide builds for python3
Product:	[Fedora] Fedora EPEL	Reporter:	Raphael Groner <projects.rg>
Component:	python-tox	Assignee:	Miro Hrončok <mhroncok>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	itamar, mhroncok, mrunge, projects.rg
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-21 08:45:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1645723

Description Raphael Groner 2019-02-21 02:01:43 UTC

Description of problem:
EPEL7 has a package for python2 only. Please provide updates for python34 (3.4) and 36 (3.6) as those currently available versions of Python.

Version-Release number of selected component (if applicable):
-

How reproducible:
yes

Steps to Reproduce:
1. dnf install python34-tox
2. dnf install python36-tox
3.

Actual results:
error: no packages found.

Expected results:
packages install properly.

Additional info:
We'll need at least python34, esp. for python-slacker (bug #1659759).
There's already python3-tox in Fedora branches, for a fix it might be sufficient to do a merge into epel7 branch.

Comment 1 Miro Hrončok 2019-02-21 06:20:34 UTC

Please see also https://src.fedoraproject.org/rpms/python-tox/pull-request/8

"I wonder why do you need a specific Python version of tox? What are you trying to achieve with this exactly? Do you import tox from Python code?"

Comment 2 Raphael Groner 2019-02-21 06:29:12 UTC

Hi Miro,

can you elaborate with more details? I fail to see what's the cause.

Well, my second try to build in epel7 worked without any of this issue mentioned. Maybe it works in mock but not local?

Really confusing.

Comment 3 Miro Hrončok 2019-02-21 06:57:31 UTC

I'm not saying it is not possible. It certainly is.

I'm saying it brings no benefit. What's your use case? What are you trying to do? Why do you need python3X-tox? How do you intend to invoke tox?

Comment 4 Raphael Groner 2019-02-21 07:36:13 UTC

> Additional info:
> We'll need at least python34, esp. for python-slacker (bug #1659759).
> There's already python3-tox in Fedora branches, for a fix it might be sufficient to do a merge 
> into epel7 branch.

Maybe we've a misunderstanding here.

Comment 5 Miro Hrončok 2019-02-21 14:55:10 UTC

FWIW I've just verified that python-slacker builds and tests without (python3-)tox.

Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.ZF0lll
+ umask 022
+ cd /builddir/build/BUILD
+ cd slacker-0.12.0
+ /usr/bin/python3 setup.py test
running test
running egg_info
writing slacker.egg-info/PKG-INFO
writing dependency_links to slacker.egg-info/dependency_links.txt
writing requirements to slacker.egg-info/requires.txt
writing top-level names to slacker.egg-info/top_level.txt
reading manifest file 'slacker.egg-info/SOURCES.txt'
writing manifest file 'slacker.egg-info/SOURCES.txt'
running build_ext
test_get_item_id_by_name (tests.test_utils.TestUtils) ... ok
test_get_channel_id (tests.test_channels.TestUtils) ... ok
test_get_channel_id_without_channel (tests.test_channels.TestUtils) ... ok

----------------------------------------------------------------------
Ran 3 tests in 0.002s

OK
+ exit 0