On 14. 05. 19 18:27, Kevin Fenzi wrote:
On 5/14/19 6:47 AM, Randy Barlow wrote:
On Tue, 2019-05-14 at 14:50 +0200, Miro Hrončok wrote:
Could you please fix python-kitchen long standing build failures or
alternatively stop using it in infra tools and retire it?
Kitchen takes the wrong approach to string encoding - I recommend that
we stop using it and retire it. It can be a dangerous library if its
string encoding stuff is used for anything security related, and it's
still bad otherwise because it hides all encoding exceptions from you,
which means you will get corrupted data in your applications.
I have no horse in this race, but if we retire python-kitchen, someone
needs to go though the things that now depend on it and remove that
dependency. ;(
I guess short term I could make it build (I got it just working mostly,
but failing a test), but that doesn't help too long with python2
retirement coming soon. Might give us a little breathing room though?
Making it build is my primary concern.
Stopping using it is my secondary unsolicited advice.
While the Python 2 retirement will certainly mess with things, the issue I have
is with kitchen usage on Python 3 (where unicode/bytes is done right, but
kitchen makes it python2ish again).
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
