Curious to hear your reasoning as to why yaml is less desirable? Would think the opposite.
Surprised me with your strong opinion.
Maybe if you would allow, and have a few shot glasses handy, could take a stab at changing your mind.
But first list all your reservations concerning yaml
Relevent packages I wrote that rely on yaml
pytest-logging-strict
sphinx-external-toc-strict
v1.8.1 was release on 2025-03-17
So pynput is being maintained. BUT there are current 155 open issues and 23 PRs. This means nothing besides this is a popular package.
v1.8.1 Changes
Mentioned that a PR dealt with a Xorg backend issue. Don’t know if this addresses your particular issue.
What pynput version do you have in your venv?
Run this command please to get the package version
python -m pip list | grep pynput
Can understand your issue report would be buried in all the other issues. So help there might not come within a timely manner.
The next step would be to create a pytest file to be able to repeat the tests, rather than run them each time manually. Obviously logging in and out is not possible. But it’s probably also completely unnecessary.
I use Xorg and Linux. Competent enough with pytest (author of pytest-logging-strict).
Before roll up my sleeves want you to confirm v1.8.1 still has this issue.
Having good intentions you tried and found out the hard way that in fact packaging does matter.
You were tricked.
I looked at it, recognized the flaming turd being thrown at the proverbial wall, and dodged.
That is our job when doing code reviews and offering advice. Be kind up to the point where being honest is unavoidable.
A series of scripts does not make a package. Have to put our collective foot down; follow Nancy Reagon’s advice, Just say no!
This project cannot be helped. It needs a complete rewrite.
Having minimal expectations is not being mean to noobs. Not getting anywhere in the ballpark of minimal expectations is being mean to potential users …
Using match is virtue signaling that have no intention of creating a working package.
What’s next on the list of crap could all live without?
colorama
six
pyyaml
Why? It’s not a package? There are no tests or anything else. It’s held together with duct tape, hope, and good intentions. So of course it’ll not work as intended.
If you encounter any issues or bugs, let me know so I can fix them!
You shoulda lead with that. I love the humor. Can’t stop laughing,
The entire project is a bug LOL!
Start with a pyproject.toml and work from there.
Everything is a bug until it’s got test coverage.
In the .github folder?! That’s gotta be a 1st
Expecting pre-commit as well as isort, flask, black, and mypy
Looked into requirements.txt expecting to find a console UI framework. There is none!
A pattern has emerged that many Python coders have spent not enough to no time learning packaging, dev toolchain, and CI/CD publishing. When asking folks to test your work they’ll be expecting a published package, not a series of amateurish scripts and a bash install script.
Please someone skilled at console UI and packaging please please please help in a paid position.
Can confidently say, you need help.
Not writing more features the OP is good at that. Just packaging and swapping out the prehistoric console UI with a modern console UI framework.
Wow that’s neat! Thanks for bringing this up.
The feature flags example should be rewritten to use enum.Flag
Mix and match to plan your day
will i be going home today?
>>> OUTRAGED_BY_NEWS = 0b00000001
>>> GET_A_COFFEE = 0b00000010
>>> GO_FOR_A_HIKE = 0b00000100
>>> GO_FOR_A_RUN = 0b00001000
>>> GO_HOME = 0b00010000
>>> various_flags_ored_together = GET_A_COFFEE | GO_FOR_A_RUN | GO_HOME
>>> various_flags_ored_together & GO_HOME == GO_HOME
True
>>> various_flags_ored_together & GO_FOR_A_HIKE == GO_FOR_A_HIKE
False
>>> various_flags_ored_together = GET_A_COFFEE | GO_FOR_A_RUN | GO_HOME
>>> bin(various_flags_ored_together)
'0b11010'
>>> various_flags_ored_together & OUTRAGED_BY_NEWS == OUTRAGED_BY_NEWS
>>> False
>>> bin(OUTRAGED_BY_NEWS)
>>> '0b1'
>>> various_flags_ored_together >> OUTRAGED_BY_NEWS
>>> bin(various_flags_ored_together)
'0b1101'
Guess haven’t gone for a hike today…maybe tomorrow
right shift removes bit at flag position. Which, in this case, happens to correspond to the right most bit.
For those looking to check file access permissions there is the stat module
>>> import stat
>>> from pathlib import Path
>>> path_f = Path.home().joinpath(".bashrc")
>>> stat.S_IRUSR
256
>>> path_f.stat().st_mode
33188
>>> is_owner_read = path_f.stat().st_mode & stat.S_IRUSR == stat.S_IRUSR
>>> is_owner_read
True
>>> path_f = Path("/etc/fstab")
>>> is_other_write = path_f.stat().st_mode & stat.S_IWOTH == stat.S_IWOTH
>>> is_other_write
False
Assumes ~/.bashrc exists, if not choose a different file you are owner and have read access to.
path_f.stat().st_mode & stat.S_IRUSR == stat.S_IRUSR
Looking thru the mundane file (not Linux access control list) permissions. All those flags are crammed into st_mode. In st_mode, on/off bit at 2^8 is that on?
Sources
read user access stat.S_IRUSR
write others access stat.S_IWOTH
Sorry
Is that a quote from Forest Gump movie?
Slightly healthier words of wisdom
Only so much humor can take on an empty stomach
from multiprocessing import Lock
l = Lock()
flake8 … way too ambiguous
so what if it’s 100x slower /nosarc
You are in for a real treat!
Here is how to step in and get the locals
This technique depends on there being only one return statement
https://logging-strict.readthedocs.io/en/stable/code/tech_niques/context_locals.html
Multiple return statements is unusual. In very rare situations i understand. But the rule is never do that.
When there is only one return statement, can step into the function to see the local variables
The sample code for lazy imports looks wrong
STRIPE = None
def _stripe():
global STRIPE
if STRIPE is None:
import stripe
return stripe
return STRIPE
STRIPE is never changed. And two return statements in the same function?!
Anyways can imagine how to do lazy imports without relying on the given code sample.
so does zfs, so does wayland, so does trying out every distro, so does trying out every text editor and associated plugins, so does trying out ventoy, so does GrapheneOS, …
Everything makes life easier, but comes down to,
Linux isn't free, it costs you your time
Which can be reframed, what do you really want to spend your time on?
If i really really really had to answer that overly honestly, want:
my GUI apps non-blocking on heavy background processes
distributing out tasks to many computers and runners
None of which screams or necessitates systemd or zfs or wayland or trying out every distro, every text editor every plugin, ventoy, or GrapheneOS.
Not in a house with a fox with a crow and a bow a knot on a cot or relaxed in the snow, i will not eat never ending random suggestions Sam, i will never eat them Sam i am.
Packaging seems to be a separate skill. Separate from coding. Lots of people are good at coding. Then hit the packaging roadblock.
Can step in and white knight, but too many projects are like that.
How to separate requirements handling and build backend
then drain-swamp (+drain-swamp-action) which supports build plugins with built in plugin for specifying semantic version.
Prefer to tell the builder the desired version rather than to be told. Options: ‘tag’, ‘current’, or specify the version. Version bump is silly.
This way can set the semantic version before tagging a release.
This is hardcore. Not for noobs, the faint of heart, or wise guys. If you don’t need build plugins then maybe drain-swamp is not for you. If you are doing something in setup.py, that you can’t live without, then might have a looksie at drain-swamp.
No, that’s… against community rules :) I don’t like the common use of venvs or .toml very much and I don’t like their use by other people and “timid” is also diplomatic. So you’re getting timid, and we get to get along and we can agree to disagree on the use of .venvs and we can wish each other a pleasant day.
Think you broke the Internet. That’s brilliant /nosarc.
Want you to write my code of misconduct!
It’s literally 10x faster
reminds me of the ol’ joke
young bull: lets run down the hill and get us a heffer
old bull: lets walk down and do 'em all
wtf is your rush?
It literally doesn’t matter how long it takes. Especially when Astral has moved on.
Very wise idea. And if you want to up your game, can validate the yaml against a schema.
Check out strictyaml
The author is ahead of his time. Uses validated yaml to build stories and weave those into web sites.
Unfortunately the author also does the same with strictyaml tests. Can get frustrating cause the tests are too simple.