Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing package: rapidfuzz #306

Closed
2 of 4 tasks
Jackenmen opened this issue Jun 16, 2022 · 4 comments
Closed
2 of 4 tasks

Missing package: rapidfuzz #306

Jackenmen opened this issue Jun 16, 2022 · 4 comments

Comments

@Jackenmen
Copy link

Jackenmen commented Jun 16, 2022

Package name

rapidfuzz

Package version

=2.0.0

PyPI URL

https://pypi.org/project/rapidfuzz/

piwheels URL

https://www.piwheels.org/project/rapidfuzz/

Python version

  • Python 3.5
  • Python 3.7
  • Python 3.9

I am the maintainer

  • Yes

More information

May be related: rapidfuzz/RapidFuzz#223
Python 3.5 is not supported by rapidfuzz >=2.0.0 so I didn't tick the Python 3.5 version in the bullet list above.

@bennuttall
Copy link
Member

bennuttall commented Jun 16, 2022

        × Getting requirements to build wheel did not run successfully.
        │ exit code: 1
        ╰─> [16 lines of output]
            Traceback (most recent call last):
              File "/tmp/tmpuvcj2fzk_in_process.py", line 363, in <module>
                main()
              File "/tmp/tmpuvcj2fzk_in_process.py", line 345, in main
                json_out['return_val'] = hook(**hook_input['kwargs'])
              File "/tmp/tmpuvcj2fzk_in_process.py", line 130, in get_requires_for_build_wheel
                return hook(config_settings)
              File "/usr/local/lib/python3.9/dist-packages/setuptools/build_meta.py", line 177, in get_requires_for_build_wheel
                return self._get_build_requires(
              File "/usr/local/lib/python3.9/dist-packages/setuptools/build_meta.py", line 159, in _get_build_requires
                self.run_setup()
              File "/usr/local/lib/python3.9/dist-packages/setuptools/build_meta.py", line 174, in run_setup
                exec(compile(code, __file__, 'exec'), locals())
              File "setup.py", line 35, in <module>
                version=versioneer.get_version(),
            AttributeError: module 'versioneer' has no attribute 'get_version'
            [end of output]

It looks like the same issue as here: #227 (comment)

You might want to raise this with the maintainers. In the mean time I will try to build offline without versioneer.

@bennuttall
Copy link
Member

Oh actually that was the error for an older version. The latest version fails with:

2022-06-16T21:29:12,201   Using FetchContent to load Taskflow
2022-06-16T21:29:13,365   [1/9] Creating directories for 'taskflow-populate'
2022-06-16T21:29:13,365   [1/9] Performing download step (git clone) for 'taskflow-populate'
2022-06-16T21:29:13,366   Cloning into 'taskflow-src'...
2022-06-16T21:29:13,366   fatal: transport 'https' not allowed
2022-06-16T21:29:13,367   Cloning into 'taskflow-src'...
2022-06-16T21:29:13,367   fatal: transport 'https' not allowed
2022-06-16T21:29:13,367   Cloning into 'taskflow-src'...
2022-06-16T21:29:13,368   fatal: transport 'https' not allowed
2022-06-16T21:29:13,368   -- Had to git clone more than once:
2022-06-16T21:29:13,368             3 times.
2022-06-16T21:29:13,369   CMake Error at taskflow-subbuild/taskflow-populate-prefix/tmp/taskflow-populate-gitclone.cmake:31 (message):
2022-06-16T21:29:13,369     Failed to clone repository: 'https://github.com/taskflow/taskflow.git'

This is because piwheels prevents packages from invoking git clone during build.

@maxbachmann
Copy link

This is because piwheels prevents packages from invoking git clone during build.

Hm, I guess I could add them back into the sdist to solve this. In addition the following change is probably required to get the package to build again piwheels/piwheels#317

@Jackenmen
Copy link
Author

Jackenmen commented Jun 23, 2022

The latest version of rapidfuzz (2.0.14) was built successfully so I think this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants