Le mer. 3 juin 2020 à 23:29, David Galloway <dgallowa@xxxxxxxxxx> a écrit :
Wait, I thought the default teuthology_branch was py2 now.
See https://github.com/ceph/teuthology/pull/1490#issuecomment-637624786
and below
David, could you help create a PR backporting the master change to nautilus?
On 6/3/20 11:25 AM, kefu chai wrote:
> hi folks,
>
> nautilus's qa/ is now py3 compatible now. so the only release branch
> which needs the "--teuthology-branch py2" option is now octopus. and i
> am working on backporting py3 changes to it. please stay tuned.
>
> On Tue, Apr 14, 2020 at 3:39 PM kefu chai <tchaikov@xxxxxxxxx> wrote:
>>
>> hi folks,
>>
>> we just migrated ceph:teuthology and all tests under qa/ in ceph:ceph
>> to python3. and from now on, the teuthology-worker runs in a python3
>> environment by default unless specified otherwise using
>> "--teuthology-branch py2".
>>
>> which means:
>>
>> - we need to write tests in python3 in master now
>> - teuthology should be python3 compatible.
>> - teuthology bug fixes should be backported to "py2" branch.
>>
>> if you run into any issues related to python3 due to the above
>> changes, please let me know. and i will try to fix it ASAP.
>>
>> currently, the tests under qa/ directories in ceph:ceph master branch
>> are python2 and python3 compatible. but since we've moved to python3,
>> there is no need to be python2 compatible anymore. since the sepia lab
>> is still using ubuntu xenial, we cannot use features offered by
>> python3.6 at this moment yet. but we do plan to upgrade the OS to
>> bionic soon. before that happens, the tests need to be compatible with
>> Python3.5.
>>
>> the next step is to
>>
>> - drop python2 support in ceph:ceph master branch, and
>> - drop python2 support in ceph:teuthology master.
>> - backport python3 compatible changes to octopus and nautilus to ease
>> the pain of backport
>>
>> --
>> Regards
>> Kefu Chai
>
>
>
Regards
Kefu Chai
Kefu Chai
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
