Closed KoichiYasuoka closed 3 years ago
Thanks for the heads up, I'll look at why this is happening. Like you say it's probably related to setuptools_scm...
In a virtualenv, I can reproduce the v0 issue, but if I install setuptools-scm first then the version number is generated correctly. So that should be a workaround for the time being.
setuptools-scm is already specified in setup-requires, so it's unclear to me why the build would work (implying Cython was used) but the version would be wrong. I'll need to look at this in more detail.
This seems to be a distutils vs setuptools issue. I pushed a new alpha version, v1.1.0a1
, can you confirm it works?
Thank you @polm, I got v1.1.0a2
work well:
$ pip3 install fugashi==1.1.0a2 --no-binary fugashi
Collecting fugashi==1.1.0a2
Downloading fugashi-1.1.0a2.tar.gz (336 kB)
|████████████████████████████████| 336 kB 303 kB/s
Skipping wheel build for fugashi, due to binaries being disabled for it.
Installing collected packages: fugashi
Attempting uninstall: fugashi
Found existing installation: fugashi 1.0.1
Uninstalling fugashi-1.0.1:
Successfully uninstalled fugashi-1.0.1
Running setup.py install for fugashi ... done
Successfully installed fugashi-1.1.0a2
$ pip3 list | fgrep fugashi
fugashi 1.1.0a2
I'm looking forward to official release of fugashi==1.1.0
.
When installing from sources, fugashi==1.0.1 does indicate its version 1.0.1, but fugashi>=1.0.2 do not have their versions:
It works even in Cygwin though its version-control goes broken. I suspect
use_scm_version
insetup.py
but I'm vague...