Closed h-vetinari closed 4 years ago
Thanks for catching the issue an the PR! Looks like I messed this up when switching back to rst. I need to release a 2.0.2 patch on pypi for the windows users :)
No problem! :)
@h-vetinari So did the importlib-metadata
made the conda-forge pipeline more complicated? Looking at the other options, I think I can remove importlib-meta requirement and just import pwlf.version in the setup.py file.
@cjekel
Everything is automated, so don't worry about the longer runtime. I'd much rather have it like that, then runtime-depend on setuptools
. If you can avoid importlib-metadata
, there are some small gains in decreasing complexity, but OTOH, we wouldn't have caught the windows bug otherwise. ;-)
For the conda-forge packaging efforts, we initially went with
noarch
, which means that only one package gets built, because the package shouldn't depend on any OS- or python-version-specific things (like compilers).However, to accommodate the update for
2.0.1
in https://github.com/conda-forge/pwlf-feedstock/pull/1 (namely the distinction to useimportlib-metadata
only onpython>=3.8
), I had to disable thenoarch
setting, which meant that then all builds got done separately. This uncovered an error on windows, becauseREADME.rst
apparently has some non-ASCII signs, and this fails becauseio.open
on windows has a default ofencoding=cp1252
.Fortunately, the fix is simple.