Closed ToasterUwU closed 1 year ago
@rsnitsch Have a look, and feel free to merge if you are ok with this.
I use this exact same thing in many of my Python projects, it helps a lot to minimize upkeep and also prevents many of the basic issues that can arise ( unbound vars, wrong types, etc. )
In case you arent familiar, everything used in here is free to use, so even tho this takes processing power, Github doesnt charge you for it.
Just realized i need to change it to use pipenv instead ( I don't use that )
Very promising, thank you.
Ok, i have never used pipenv, i need to test it really quick on my fork, just to make sure it runs fine. After that you can merge it.
Ok, i have never used pipenv, i need to test it really quick on my fork, just to make sure it runs fine. After that you can merge it.
Thank you for the extra diligence. 👌
@rsnitsch Take another look and merge if you want to. I tested this on my fork, and it worked. Meaning it screamed at me for the fact. I don't have the fixes from the #16 PR, but with them its smooth sailing.
If you wonder which to merge first, doesn't really matter.
The cleaner one would be to merge the other one first and then this one, but in the end of the day it will show "Lint Passed" as the newest status anyways.
The actual PR for #13 I will make either tomorrow or the day after, depending on what else is on my list tommorow.
Thank you very much! I merge this first because I want to see it screaming. ;-)
@rsnitsch Btw, it might make sense to add all Python versions you want to officially support to the lint workflow. Just add them to the OS matrix thing next to 3.10 and 3.11. I recommend putting 3.8 in at least because that's pre-built-in type hinting.
As promised in #13