Lint requirement version format
See original GitHub issueI just had an issue with a PR (https://github.com/conda-forge/staged-recipes/pull/6025) where I used an invalid requirement string traittypes >= 0.2
. Here, the last space (between >=
and 0.2
) should be removed. Ideally, this should be picked up by the linter.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
python_requirement - Pants build system
A Python requirement installable by pip. This target is useful when you want to declare Python requirements inline in a BUILD file.
Read more >Requirements File Format - pip documentation v22.3.1
Requirements files serve as a list of items to be installed by pip, when using pip install. Files that use this format are...
Read more >Automatically format and lint code with pre-commit - Interrupt
This article provides some background and guidelines for using pre-commit to automatically format and lint C-language firmware codebases.
Read more >Rules | npm-package-json-lint
Rules · Require node rules · Type rules · Valid value rules · Dependency rules · Scripts rules · Format rules · Package.json...
Read more >Improve your code with lint checks - Android Developers
The lint tool checks your Android project source files for potential bugs and optimization improvements for correctness, security, performance, usability, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think this was fixed by https://github.com/conda-forge/conda-smithy/pull/1133
Should we actually be linting the version spec for a requirement? I recently had a typo in the spec (stray trailing
[
), which wasn’t picked up by the linter but later failed conda’s_parse_spec_str
. Could we use that function to parse version spec strings already in the linter?Happy to open an new issue for this if you prefer.