layday
layday
Yeah, I think that'd be preferable too, that it should function the same way regardless of input. Does anybody wanna take this up?
Would we perform any kind of validation then or do we assume that any gzipped tarball is an sdist?
When building with flit-core, `__pycache__` folders are only excluded from the "module" folder, so if you were to add e.g. your tests folders in the sdist, `tests/__pycache__` won't be filtered...
Python comes bundled with an older version of pip which gets installed in a fresh virtual environment such as the one created by build. The version of pip that shipped...
Actually, virtualenv has a newer version of pip, so if its pip were being used, that message would not have been emitted. There's something going on with the Python path...
I tried this with the Command Line Tools copy of Python and can confirm that a virtual environment created with `virtualenv` inherits the path of the caller - the virtualenv...
To get your project to build _with isolation_, uninstall both build and virtualenv and reinstall build from source: `python3 -m pip uninstall -y build virtualenv && python3 -m pip install...
This is unrelated to #271 if that's what you mean.
https://github.com/pypa/packaging-problems/issues/558
It expects the fully-qualified module name, which in this case would be `setuptools.config.setupcfg`. You can filter using regexes with the programmatic API but not with `-W` or the env var.