The master of teuthology is py2 only yet, the rest py3 code is py3 compatibility PR which is NOT merged yet.

The official way (the tested one by jenkins pull request job) is to run bootstrap script.
Some time the bootstrap was patched to workaround setup tools issue for py2

https://github.com/ceph/teuthology/commit/8aef0dfea2c8fcdf13818a762ac1512ab1956ff5


Kyrylo Shatskyy
--
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nuremberg
Germany


On Mar 4, 2020, at 3:45 PM, kefu chai <tchaikov@gmail.com> wrote:

On Wed, Mar 4, 2020 at 10:22 PM Patrick Donnelly <pdonnell@redhat.com> wrote:

On Wed, Mar 4, 2020 at 3:08 AM kefu chai <tchaikov@gmail.com> wrote:

On Wed, Mar 4, 2020 at 10:43 AM Gregory Farnum <gfarnum@redhat.com> wrote:



On Tue, Mar 3, 2020 at 6:19 PM Patrick Donnelly <pdonnell@redhat.com> wrote:

On Tue, Mar 3, 2020 at 3:12 PM Dan Mick <dmick@redhat.com> wrote:

On 3/3/20 11:05 AM, Patrick Donnelly wrote:
$ rm -rf venv/ && (virtualenv -p python2 ./venv && source
venv/bin/activate && pip install --upgrade pip && pip install -r
requirements2.txt && python2 setup.py develop)
...
Collecting typing; python_version < "3.4.0"
  Using cached typing-3.7.4.1-py2-none-any.whl (26 kB)
Requirement already satisfied: setuptools in
./venv/lib/python2.7/site-packages (from pytest==3.7.1->-r
requirements2.txt (line 84)) (45.0.0)
ERROR: Package 'setuptools' requires a different Python: 2.7.12 not in '>=3.5'

Anybody know what changed or how to fix this? My usual bash one-liner
to update my virtualenv failed with this packaging issue.

could you pastebin the full output? i cannot find which package
required Python >= 3.5 in this snippet .

https://paste.centos.org/view/a33606f3

i think the root cause is that one cannot install setuptools without
specifying its version if working on python2 because
https://github.com/ceph/teuthology/pull/1394 .


sure looks like you need python3?

teuthology is now python3 only?


Kyr has been working on python3 compatibility but I don’t think it’s done or required yet.

You might try just deleting your virtualenv and re-./bootstrap’ing which is what I generally do.

It looks like "./boostrap" works. I was doing the old manual process.
Thanks everyone.

--
Patrick Donnelly, Ph.D.
He / Him / His
Senior Software Engineer
Red Hat Sunnyvale, CA
GPG: 19F28A586F808C2402351B93C3301A3E258DD79D



-- 
Regards
Kefu Chai