Antoine Dechaume
Antoine Dechaume
I cannot reproduce it: ``` ll total 8.0K -rw-r--r-- 1 antoine 38 Nov 21 20:36 setup.py -rw-r--r-- 1 antoine 53 Nov 21 22:07 tox.ini cat setup.py from setuptools import setup...
Thank you, I can reproduce it now.
Meanwhile, just install `tox` (no `tox-conda`) in your anaconda environment: ``` conda create -c conda-forge -n toxcondabug python=3.8 tox ... conda run -n toxcondabug --no-capture-output tox .tox create: /tmp/0/.tox/.tox .tox...
I think that [requires](https://tox.wiki/en/latest/config.html#conf-requires) refers to the packages installed in the provisional environment from where tox is executed from, and not to the environments from where the [commands](https://tox.wiki/en/latest/config.html#conf-commands) are executed....
Hi @koxudaxi, it looks like you've rebased this PR, the failing CI jobs are due to codecov. Do you need me to do something?
@koxudaxi > Btw, How do we set `"null"` string value as default? I do not know. > Also, Can we use `"default": null` for default? I would say yes in...
I use version 3.0.19, but being stuck on redhat 5 I understood that I shall not go beyond that version.
I updated to conda-build 3.0.27, thx! Unfortunately the issue remains.
At the time of the initial issue, I did find a workaround, but after I updated conda-build to 3.8 (still on RHEL 5), I'm facing a similar issue where `version`...
It actually has nothing to do with the `version` key, I managed to reproduce the issue with the following recipes: - `x/meta.yaml` ``` package: name: x version: {{ bar }}...