the old way i am fine with
Never ever made a mistake and install anything system wide
don’t need white knights or a nanny state to keep us safe
the old way i am fine with
Never ever made a mistake and install anything system wide
don’t need white knights or a nanny state to keep us safe
then they come after our guns, but spoons are always magically safe
To all the fat slob system wide installation cock blocking PR submitters, i say,
Ban spoons!
Shooting ourselves in the foot is a G’d given right! /nosarc
Yes
Whats the alternative you are advocating for?!
We need AA meetings
Hello!
My name is Billy Joe Jim Bob
Hello Billy!
I haven’t had a dependency conflict for the past 3 hours. The sleeping problems haven’t gone away. As i feel my eye lids drupe, keep thinking about each of my packages and imagining where will the next unresolvable dependency conflicts emerge.
Then i wake up covered in sweat.
Can’t keep going on like this. Thank you for listening
Thank you for sharing Billy!
Same thing said another way, be open to using more than one venv
So these package maintainers are harboring magical charms and voodoo dolls which us lowly plebs just don’t know about?
If these guys are so awesome, shouldn’t we be plying them with coke and blow and keep 'em working resolving our dependency resolution issues?
They do have the secret sauce and just holding it back from the rest of us
Don’t wanna be that guy who gaslights you.
If you are having issues, should be pointing us at a repo
pip is great! It lets ya know when there are dependency conflicts.
Up to us to learn how to deal with resolving dependency conflicts.
There are those who attend the whining parade down main street.
There are the very very few who write a package to resolve these issues.
the one venv to rule them all
is not a viable solution.
Some packages cause problems, one tactic is to isolate the problem package into a separate venv.
For example
.venv/
– main venv for the dev setup
.doc/.venv
- Sphinx docs (now minimum py310)
.wth
for e.g. package restview which has out of date dependencies.
Each venv has its respective requirements files. Some associated with a dependency or optional dependency. The ones that aren’t are pin files.
Lets say there are easily a total of 20 requirements and constraints (pin files).
This mess is in a freak’n nasty multi level hierarchy.
Now imagine you are the author maintainer of 10 packages. Can you be confident one package requirements won’t conflict with other packages requirements?
Almost forgot
these packages are no longer maintained:
pip-tools
pip-requirements-parser
… scary
libtorrent C++ with Python bindings
On Linux, would install it from the package manager.
deleted by creator
deleted by creator
deleted by creator
deleted by creator
Often using pytest to debug code. When using a tmp_path, would prefer not to delete the file tree in the end.
When the test fails, can run the code against the folder tree
cd
into the tmp folderBesides showing off what a degenerate can accomplish.
I can run groupings or part of a grouping of unittest testcases in parallel. From a GUI. By typing ~6-10 keystrokes.
Just never got around to implementing this using pytest. And cuz of that, never published the GUI package.
Search algorithms matter
When humans read ^^ nothing registers in the brain. Could write it 1000x and would always fall on closed brains.
People would still go back to recommending their favorite File Managers (has no search algo) or managing their contacts within each social media platform. And infinite scroll new feeds.
Without thinking twice about it.
Use both unittest and pytest. To get proficient in both.
Was initially thinking this article is going to turn out to be useless. Then it taught a useful trick that wasn’t aware of.
Learning something new with unittest is unusual.
Yeah saw that. It’s awesome you are responsive. Gave the project a star cuz it deserves it!
Sent two other issues your way. One just a file rename. The other specifying authors contact info.
Should add this as an issue
This could lead to the girl having a legitimate reason for declining a marriage proposal from a TG bot
Would the coke and blow happen for that guy?
Makes sense if i’m that guy
This question is about Python package funding. If world+dog no longer stresses over pip dependency resolution isn’t this not extremely valuable? So how to go about getting that package permanently funded. No bs dangling a tiny carrot and insisting on strict justice (reporting milestones …). Then funding only happens for large projects.
Question on package funding is very legitimate. Have a list of packages that are no longer maintained cuz funding never happened.
Can subsist on crocodile tears. It’s a guilty pleasure.
Meaning, if package funding never ever happens, and all that ever happens is never ending articles/threads on Python devs whining about dependency resolution, i’m going to feed that.
Personally not suffering from dependency resolution stress. Everyone else does.
If the available solutions were sufficient there would be no more articles with comment sections filled with war stories, tales of carnage, and loss.
… always comes down to that one guy.
Solve the Python author maintainer funding issue!
Then and only then will i market the package that specifically targeted towards resolving pip dependency resolution issues for package (and app) maintainers.