Search Criteria
Package Details: python-flake8-quotes 3.3.2-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/python-flake8-quotes.git (read-only, click to copy) |
---|---|
Package Base: | python-flake8-quotes |
Description: | Flake8 lint for quotes |
Upstream URL: | https://github.com/zheller/flake8-quotes |
Licenses: | MIT |
Submitter: | acxz |
Maintainer: | dmitmel |
Last Packager: | dmitmel |
Votes: | 4 |
Popularity: | 0.020340 |
First Submitted: | 2020-05-30 22:42 (UTC) |
Last Updated: | 2024-04-08 12:52 (UTC) |
Dependencies (6)
- flake8
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-setuptools (make)
- python-wheel (make)
- python-pytest (check)
Required by (4)
- papis-git (check)
- python-flakeheaven
- python-flakehell
- python-roonapi (make)
Latest Comments
1 2 Next › Last »
dmitmel commented on 2024-04-08 12:51 (UTC)
I'm going to just disable this one test since making it work has been more trouble than it's worth (basically seems to be double-checking the builtin functionality of flake8 of being able to run plugins when reading input from stdin).
gesh commented on 2024-04-08 12:17 (UTC)
Couldn't reproduce -- could you try https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot (ie install
devtools
, thenpkgctl build
)?Andrei_Korshikov commented on 2024-04-08 10:33 (UTC)
gesh commented on 2024-03-26 20:45 (UTC) (edited on 2024-03-26 20:46 (UTC) by gesh)
OK, found a workaround:
gesh commented on 2024-03-26 20:05 (UTC)
For some reason, it appears
python setup.py test
manages to runflake8
with our package plugged in, whereaspython -m {py,unit}test
both run it in a clean environment. I've disabled the offending test in the below -- have run out of patience trying to massage it into success.gesh commented on 2024-03-26 17:54 (UTC)
And indeed, checking it in this way reveals my implementation of
check()
is wrong, though I don't know why. Butpython setup.py test
differs in behaviour frompython -m unittest
gesh commented on 2024-03-26 17:39 (UTC)
You are correct, my bad. Yeah, PEP517 only controls the invocation of the build process, but at the end of the day you still need the the build backend, in this case
python-setuptools
. Nice catch!dmitmel commented on 2024-03-26 16:52 (UTC)
gesh: Shouldn't
python-setuptools
be present in the dependencies as well?gesh commented on 2024-03-26 16:43 (UTC)
This is what I had in mind:
gesh commented on 2024-03-25 21:40 (UTC)
https://wiki.archlinux.org/title/Python_packaging_guidelines#Standards_based_(PEP_517)
Python decided to change the way they recommend installing packages a short while back, and so even if the project doesn't have a
pyproject.toml
the instructions from the wiki should be followed - that is, using1 2 Next › Last »