Previously, upstream of chardet kept separate codebase for Python 2 and 3. This has changed and they only keep one code for all. I'm proposing to retire python3-chardet and build python3-chardet as a subpackage of python-chardet. The benefit is to keep things simple and have less work in future when updating. I'm willing to do the necessary update of python-chardet if gained consent.
(In reply to Miro Hrončok from comment #0) > Previously, upstream of chardet kept separate codebase for Python 2 and 3. > This has changed and they only keep one code for all. Great! > I'm proposing to retire python3-chardet and build python3-chardet as a > subpackage of python-chardet. The benefit is to keep things simple and have > less work in future when updating. In principle, yes. I don't know the current state of the effort of using python3 as default. Maybe we would need to rename all python-* packages to python3-* and leave the python-* ones as "the ones using python2"? Do you maybe know, how exactly this transition will go on? > I'm willing to do the necessary update of python-chardet if gained consent. I concur, please do the necessary update (if we won't have to re-review python3-chardet because of the above...). Thanks! :)
(In reply to Thomas Spura from comment #1) > Maybe we would need to rename all python-* packages to > python3-* and leave the python-* ones as "the ones using python2"? > Do you maybe know, how exactly this transition will go on? I don't know exactly how the transition will work, but python- prefixed SRPMs are going to stay. Maybe both Python 2 and Python 3 packages would be a submodule of that (rally just maybe), but I know that mergning python3-chardet and python-chardet to python-chardet is not a step aside.
s/submodule/subpackage
(In reply to Miro Hrončok from comment #2) > (In reply to Thomas Spura from comment #1) > > Maybe we would need to rename all python-* packages to > > python3-* and leave the python-* ones as "the ones using python2"? > > Do you maybe know, how exactly this transition will go on? > > I don't know exactly how the transition will work, but python- prefixed > SRPMs are going to stay. Maybe both Python 2 and Python 3 packages would be > a submodule of that (rally just maybe), but I know that mergning > python3-chardet and python-chardet to python-chardet is not a step aside. Ok, them I'm all in.
Kushal is also in favor (confirmed on IRC)
Thomas, please go ahead and retire python3-chardet in pkgdb (I've done it in git): $ pkgdb-cli orphan --retire python3-chardet master
http://koji.fedoraproject.org/koji/taskinfo?taskID=7100528
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
(In reply to Miro Hrončok from comment #6) > Thomas, please go ahead and retire python3-chardet in pkgdb (I've done it in > git): > > $ pkgdb-cli orphan --retire python3-chardet master Done, thanks for working on it!
Thanks for your cooperation.