• 5 Posts
  • 129 Comments
Joined 1 year ago
Cake day: March 1st, 2024
  • logging_stricttoLinux•I'm done with Ubuntu
    1·
    4 days ago

    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.

  • logging_stricttoPython•PEP 517 build system popularity
    1·
    7 days ago

    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.

    Warning

    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.

  • logging_strictOPtoPython•Dependency management
    21·
    7 days ago

    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!

  • logging_stricttoPython•A year of uv: pros, cons, and should you migrate
    11·
    7 days ago

    It’s literally 10x faster. I’m not sure what kind of person wouldn’t care about that. On that, lets agree to disagree.

    Thru magic Astral has funding. I don’t. So why shoulder the risk that their magical situation will continue forever.

    When Astral goes tits up, which we seem to agree on, and everyone is whining crying and screaming, at least there is one or more fallback(s) written in Python which is/are maintainable by people without magical super powers.

  • logging_strictOPtoPython•Dependency management
    11·
    7 days ago

    I have no need for this kind of tool, because I don’t have version conflicts. Does this manage my dependencies in other ways?

    Happily no. wreck attempts to do only one thing. If you don’t have version conflicts in your requirements files then whatever you are doing, keep doing that.

    No idea what .in is.

    requirements-*.in. are placed in folders. So requirements/whatever.in --> requirements/whatever.lock and requirements/whatever.unlock

    Are they still .txt or is there a new file standard for .lock and .unlock?

    .txt is meaningless or exceedingly broad. A text file huh? Well that explains everything.

    The standard is what works.

    use of venvs

    Containerization, especially for GUIs and apps, is better than depending on venvs. Until it’s not. Then still need venvs

  • logging_stricttoPython•Critique This! A Simple Qt Dock Widget which enables the whole widget to be 'folded' to use less screen space
    11·
    7 days ago

    The same argument can be made for supporting Windows and MacOS. Don’t have these dev environments. But somehow found a way to support these platforms.

    If you look into it, pyQt[x] and pySide[x] aren’t all that different. The intent of PySide is to keep them for the most part compatible.

    Don’t have to manage everything, just what is being used.

    Doing the wrong thing explains most my packages:

    wreck – dependency management

    drain-swamp with drain-swamp-action – build backend with build plugins

    logging-strict – strictly validated logging configuration

    pytest-logging-strict – the same thing except a pytest plugin

    What else am i not supposed to do?

  • logging_stricttoLinux•I'm done with Ubuntu
    1·
    7 days ago

    There is lots of complexity creep. And i’m one person with a finite lifespan. So had to decide what to spend time on.

    systemd is ideal for those running servers. I’m publishing Python packages and wanted to keep focused on that.

    If you wish to work for me for free, cuz i have zero access to labor or funding, to upgrade my tech infrastructure, i could be a useful person to know.

    Especially if you believe strongly i should be running much better infrastructure.

  • logging_strictOPtoPython•Dependency management
    11·
    7 days ago

    Why have you been keeping this a secret?

    I have. Wanted to see if anyone would find a published pypi.org package organically, w/o any marketing.

    Surely with a trillion eye balls and the super powers of AI, it would be impossible to hide something in plain sight, Right? Especially on the most important topic in Python.

    Now the question becomes, does the world+dog ignore federated social media? Is every coder required to have a blog?

  • logging_stricttoPython•A year of uv: pros, cons, and should you migrate
    2·
    7 days ago

    What do you do when there is/are unavoidable package dependency conflict(s)? <-- biggest question in Python

    Often times, split out into mutliple venvs.

    For example, Sphinx requires py310+. My default is py39. myst-parser restricts dependencies rather than allow the latest and greatest. So there is an unavoidable need for two venv.

    After setting up pyenv, how much setup is required, in pyproject.toml, to setup these two venv?

    Looking at poetry, it’s focused on one venv. And it’s annoying it considers pyproject.toml to be a r/w file. I want to configure for an unlimited number of venv.

  • logging_stricttoPython•A year of uv: pros, cons, and should you migrate
    36·
    7 days ago

    The OP author is very familiar with uv, having written multiple articles on it. Pushes it onto his students. So i get it, the article is focused on uv and he is invested in uv. This assessment is a tiny bit unfair, but enough, only, to justify reading the article with a tiny grain of salt.

    For package management, i’m happy with pyenv. So there i have a bias.

    The biggest praise i have is, it follows the UNIX philosophy, do one thing and do it well. uv does multiple things, the issue comes down to resources required to maintain a super complex thing. Especially in a completely different coding language! I DONT GIVE TWO SHIATS IF ITS FASTER, I care about maintainability after the original geniuses disappear and they will.

    dependency management

    Any blog post which doesn’t mention competitors, tiny grain of salt --> giant grain of salt.

    If not mentioned, have to assume either don’t know about them or haven’t bothered to try them.

    What are the actual competitors to uv (specifically for dependency management)?

    The only package mentioned is: poetry

    poetry also violates the UNIX philosophy. It combines build backend with dependency management. I want them separate.

    Open up that super powerful doom pr0n machine, AI, and get it to find the other (dependency management packages). Mention them in the blog post.

  • logging_stricttoPython•Avoid over-commenting in Python
    1·
    8 days ago

    don’t break up long functions

    Some things are so complex they can only be understood in long functions. Break up the long functions and what’s going on is lost.

    Only have one example where the complexity is best left alone, the heart of a requirements management package. Where the whole is greater than the sum of it’s parts. Or the parts lose meaning if taken in isolation.

    docstrings

    surprised flake8+black even allows a comment as the docstring.

    Prefer triple single quotes over triple double quotes. But black slapped me back into conformance. Of course i’m right, but evidently that’s not good enough. So triple double quotes it is.

    Slap me often and hard enough, i learn conform.

    Except for build backends and requirements management.