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

Error parsing requirements for wikitextparser #57

Open
dvzubarev opened this issue Jan 10, 2022 · 1 comment
Open

Error parsing requirements for wikitextparser #57

dvzubarev opened this issue Jan 10, 2022 · 1 comment

Comments

@dvzubarev
Copy link
Contributor

pynixify wikitextparser
Resolving wikitextparser
Error parsing requirements of /nix/store/190ccpx58ga9qym1x16z1f1sx2i9wym6-wikitextparser-0.48.0.tar.gz. Assuming it has no dependencies.
Error parsing requirements of /nix/store/190ccpx58ga9qym1x16z1f1sx2i9wym6-wikitextparser-0.48.0.tar.gz. Assuming it has no dependencies.
Error parsing metadata of /nix/store/190ccpx58ga9qym1x16z1f1sx2i9wym6-wikitextparser-0.48.0.tar.gz. Assuming it has no metadata.

But it worked ok in the previous version:

pynixify wikitextparser==0.47.9
Resolving wikitextparser==0.47.9
Resolving regex; python_version != "3.5" or platform_system != "Windows" (from PyPIPackage(attr=wikitextparser, version=0.47.9))
Resolving wcwidth (from PyPIPackage(attr=wikitextparser, version=0.47.9))

wikitextparser migrated to setup.cfg in the latest version (see commit ). But I thought pynixify can handle setup.cfg.

@cript0nauta
Copy link
Owner

At the moment, pynixify doesn't handle projects with setup.cfg, since it will always try to parse the project's setup.py file, As a workaround to make pynixify work with projects depending on wikitextparser, I'd recommend to manually package wikitextparser in nixpkgs. Then you will be able to use your project with pynixify, as it will use the version of nixpkgs.

Suggestion for packaging: you can use the output of pynixify wikitextparser==0.47.9 as a starting template for packaging. if you manually change the version and hashes in the generated file, that might work ok.

Let me know if you need any help with this workaround!

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

No branches or pull requests

2 participants