-
Notifications
You must be signed in to change notification settings - Fork 172
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
[PKG SUPPORT] pylint <3
and Python 3.12
#641
Comments
Hi there, thank you for the report, I will add it to my TODO list along with pylint-dev/pylint-django#405 |
Good man, Carl! Cheers 🍺 |
Is there anything I can do to help resolve this? I'm still running into the issue originally noted in #651. |
#658 seems like a reasonable workaround to get 3.12 support out the door, but I'm also not an expert in prospector or pyroma. Assuming there are other pyroma tests in the suite, there should be some confidence that it doesn't actually break prospector's integration with pyroma. |
@ryancausey cheers, mate! That's what my take is too - also, one clue is that workaround in #658 is needed only for when tests run on Github Actions, local tests run fine without it - beats me what changes in the file that the test runs on GA, but I suspect that's just a minor change like a trailing white space or some newline char, that gets picked up by the |
@Pierre-Sassoulas was my review above of any use? |
Anything more I can do to help move this along? |
Sorry that I have been absent for a while, I will try to get onto this in the next few days... |
very happy to see you back @carlio - we was getting concerned 🍺 |
Hey fellas, a quick touching base from one of your conda-feedstock maintainers here - the new v1.10.3 builds well now conda-forge/prospector-feedstock#43 - but I had to pin upper
pylint
to<3
, see failed test withpylint=3
- and since I vaguely understand poetry environment files, I wanted to double checkpylint
is upper pinned to <3 upstream (here) too. Incidentally, Python 3.12 support seems to work fine for you, so I'd suggest you included a Github Action test for 3.12 as well (seen you guys have them all Pythons but no 3.12 GA test yet). Cheers and keep up the good work 🍺The text was updated successfully, but these errors were encountered: