Open maximlt opened 2 years ago
Maybe upgrade tox?
Given the comment above the failing line I'd rather try to find a direct solution to that, before attempting to upgrade tox which could break pyctdev in various ways.
# TODO really doubt this is the right way
return toxconf.envconfigs[env].basepython.split("python")[1]
First I'll have to understand what was the intention with this code, and if it was effectively working. There's no emergency though, not until Python 3.7 in EOL.
For a while I've observed than trying to build packages on Python > 3.7 just fails, on conda not pip. This is for instance the error I got when trying to build Lumen on Python 3.8.
After a long debugging session I could pin down the issue to the
get_tox_python
, which on Python 3.7 returns'3.7'
but returns an empty string on later versions of Python.https://github.com/pyviz-dev/pyctdev/blob/1ad27d99b1724fe5bee9bc35c07c96ede5776085/pyctdev/util.py#L39-L44
Not sure it's a bug in tox (which pyctdev vendors) or elsewhere, but at least now we know where the problem comes from! Fixing it though properly will require me to better understand how
doit package_build
works.