Questions about upcoming python 3 changes in Koji

[Kate Carcia]

Hello,

I have some questions about upcoming changes in Koji related to porting to
python 3. Since Fedora rel eng depends on this change for porting about 80%
of our rel eng scripts over to python 3, we wanted to reach out with some
questions in anticipation of this change.

First, we are wondering if these changes will affect how we interact with
the Koji library and cli. For example, should we anticipate function
signatures changes, different return values, etc.?

Second, is the Python2-Koji-Library guaranteed to continue to have
compatibility with the Python3-Koji-Server?  As noted by one of our
developers, Rob Marshall (who I've cc'ed on this email), Python3-Koji-Server
is supposed to drop in mid-July. We are currently planning to have some
overlap where we use the Python2-Koji-Library to talk to the
Python3-Koji-Server. We are concerned our calls will fail due to the
mismatch between the Python versions of the calling API versus the server.

Best,
Kate

Best,
Kate

------------------------------
Project Manager *|* RCM *|* Westford, MA
Office: [phone] *|* IRC: katec

[Kate Carcia]

Ah, my apologies. I realize this message went out twice.

Best,
Kate

------------------------------
Project Manager *|* RCM *|* Westford, MA
Office: [phone] *|* IRC: katec

On Tue, May 9, 2017 at 1:20 PM, Kate Carcia  wrote:
> Hello,
>
> I have some questions about upcoming changes in Koji related to porting to
> python 3. Since Fedora rel eng depends on this change for porting about 80%
> of our rel eng scripts over to python 3, we wanted to reach out with some
> questions in anticipation of this change.
>
> First, we are wondering if these changes will affect how we interact with
> the Koji library and cli. For example, should we anticipate function
> signatures changes, different return values, etc.?
>
> Second, is the Python2-Koji-Library guaranteed to continue to have
> compatibility with the Python3-Koji-Server?  As noted by one of our
> developers, Rob Marshall (who I've cc'ed on this email), Python3-Koji-Server
> is supposed to drop in mid-July. We are currently planning to have some
> overlap where we use the Python2-Koji-Library to talk to the
> Python3-Koji-Server. We are concerned our calls will fail due to the
> mismatch between the Python versions of the calling API versus the server.
>
> Best,
> Kate
>
> Best,
> Kate
>
> Project Manager *|* RCM *|* Westford, MA
> Office: [phone] <(857)%20770-0448> *|* IRC: katec

[Tomas Kopecek]

Dne 9.5.2017 v 19:20 Kate Carcia napsal(a):
> Hello,
>
> I have some questions about upcoming changes in Koji related to porting
> to python 3. Since Fedora rel eng depends on this change for porting
> about 80% of our rel eng scripts over to python 3, we wanted to reach
> out with some questions in anticipation of this change.
>
> First, we are wondering if these changes will affect how we interact
> with the Koji library and cli. For example, should we anticipate
> function signatures changes, different return values, etc.?
>
> Second, is the Python2-Koji-Library guaranteed to continue to have
> compatibility with the Python3-Koji-Server?  As noted by one of our
> developers, Rob Marshall (who I've cc'ed on this
> email), Python3-Koji-Server is supposed to drop in mid-July. We are
> currently planning to have some overlap where we use the
> Python2-Koji-Library to talk to the Python3-Koji-Server. We are
> concerned our calls will fail due to the mismatch between the Python
> versions of the calling API versus the server.
>
> Best,
> Kate
>
> Best,
> Kate
>
> Project Manager *|* RCM *|* Westford, MA
> Office: [phone] *|* IRC: katec
>
> koji-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

Hi,
API shall not be broken due to python3 migration.

We are aiming to move to python3 primarily with library and cli. Moving 
hub/builder to python3 doesn't make too much sense now, as there are 
dependencies which are not ported yet (or will never be). So, only 
non-breaking items will be incorporated there.

I'm trying now to cleanup all possible changes in return values (mainly 
unicode/str/bytes variations) to be fully compatible with current situation.

Most current py3 code could be found here [1]. Note, that there is more 
work done, than will be probably included in following PR (those 
hub/web/builder parts). If you'll use only library and client from here, 
you should be very near to final result. Also any comments are welcome!

[1] https://pagure.io/fork/tkopecek/koji/branch/python3-cli2