Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)L

logging_strict

@ logging_strict @programming.dev

Posts
7
Comments
319
Joined
2 yr. ago

  • The PSF has withdrawn a $1.5 million proposal to US government grant program

    Jump

  • Didn't join PSF for the same reasoning they turned down this loan. Agreeing to a code of conduct or adhering to some random foreign and self-destructive ideology (whatever that may be), at all costs, has nothing to do with coding or running an organization.

    So PSF folks are doing to us the same as the US govt is doing to them. There is no difference. Oh the irony is sweet.

    It's good these idiots are not getting US tax slave funding. Being priests of the DEI religion is more important to them than good stewardship of PSF and Python.

    And i support tech organizations and projects being well funded. Just not priests.

  • Is there a Python package to create single .md file documentation from docstrings?

    Jump

  • For the Makefile and conf.py, it's a Ctrl+P job. tox.ini more Ctrl+P. Crap that goes into pyproject.toml Ctrl+P.

    ETA ~20 mins including bathroom breaks and chatting with friends that randomly arrive at the cafe.

    Then comes dealing with fixing up the URLs and references. That is the only time consuming bit.

    Have posted links to packages i've written, can just go there and five finger discount the configuration files.

    Howto autodoc, i'm not licensed to sell without a medical license. But there is a shot for that. ;-)

  • Is there a Python package to create single .md file documentation from docstrings?

    Jump

  • Just spent the last two weeks (no exaggeration) putting documentation together. Ensuring references resolve correctly is the time consuming bit.

    extlinks, nitpick_ignore, autodoc_type_aliases, intersphinx_mapping, multiple extensions, and building inventories using sphobjinv, Table of contents using sphinx-external-toc-strict links to both ref and docs.

    The table of contents supports both .md and .rst files. With the caveat that the initial file must be index.rst.

    Having to relearn all this crap to do the same thing (e.g. mkdocs)? Would rather stick a fork in my eye.

    Here is a sample TOC config file wreck _toc.yml from package wreck. Shows globs:, file:, url: links.

    This one includes both .rst and .md strict TOC _toc.yml

    Output is a user manual web site or a pdf.

    markdown and restructuredText are input files, not the end goal.

  • Which python scaffolding tools?

    Jump

  • On this board, and hope everyone else is, to learn and share. Try to contribute, not just state my opinion.

    Didn't feel this thread offered anything substantial to learn, so threw out some gem that others might find useful in their projects.

  • Ubuntu 26.04 Looks To Retire Its ISO Tracker: "Held Together With Duct Tape & Goodwill"

    Jump

  • Have been in the exact same situation. Had a code base written in PHP that needed porting to Python. i'm still porting it.

    The lesson here is maybe you gotta hold on to what you have and then work on a replacement without throwing away the golden goose.

    Was managing a 3,500 person network.

  • Which python scaffolding tools?

    Jump

  • Package DevOPs is a skill. Half assing it will not:

    • impress a published package author's peers
    • encourage confidence in the authors perseverance to maintain the package
    • encourage confidence in the author's willingness to politely respond to Issues and PRs
    • package will have issues that never get resolved cuz the author packaging skillset is woefully lacking including but not limited to: Makefile, pre-commit, tox, gha, doctest, documentation, test coverage, multiple platform support, manylinux support, setup for collaboration, and static typing.

    So suggest redirecting efforts towards studying how to improve packaging rather than how to avoid packaging.

    A suggestion on things to improve documentation:

    move the doctest out of in-code documentation and into test suite! So the doctest are proof and contribute to coverage

     shell
        
python -m coverage run --parallel --data-file=.coverage-combine-tests -m pytest --doctest-glob="*.rst" --showlocals $(verbose_text) tests/safe tests/a tests/b

    This is straight from a Makefile. Where the file extension for doctest was changed to .rst. Can see have A B testing setup to compare two packages.

    Example how to include doctest into Sphinx document

     text
        
.. literalinclude:: ../tests/a/test_presentation.rst
    :language: pycon
    :name: unique-id
    :caption: illustrative-description

  • Release 0.0.1-alpha.22 · astral-sh/ty

    Jump

  • Until @fruitcantfly set me straight, couldn't read and understand the version str and was unaware Rust followed a different pattern than Python.

  • Release 0.0.1-alpha.22 · astral-sh/ty

    Jump

  • Thanks for the link to Cargo's versioning docs.

    In Python, packaging is authoritative. Past that version str thru packaging and it was modified.

    Honestly misunderstood, thinking there was 22 alpha releases.

    Am still misreading it. The alpha and dev portions are not distinctive enough to be clear. Didn't even see in the Cargo dev portion mentioned.

    Obviously publishing dev releases is not allowed, but in git dev commits are a thing.

  • Release 0.0.1-alpha.22 · astral-sh/ty

    Jump

  • Never even viewed Milestones before. Thanks @lens0021 for pointing them out. Link to Milestone found on both Issues and PR sections.

    Don't know why been ignoring it, maybe something like,

    "Milestones ewww scary. Might be dangerous better not click on it"

  • Internet Explorer vs. Murder Rate

    Jump

  • Was that during the period Bill Gates was still married, but enjoying plane flights with other billionaires?

  • Release 0.0.1-alpha.22 · astral-sh/ty

    Jump

  • My point is to wait for an actual release, a call to action, or an article about the project. Release notes on a dev pre-release is odd.

    Not discouraging you from posting. You are very welcome to post here. And btw thanks for responding.

    This is the semantic versioning spec, but it'll give you nightmares.

    Here are examples with explanation for each versioning component. Much easier on the eyes

    gl

  • Release 0.0.1-alpha.22 · astral-sh/ty

    Jump

  • Really don't understand why post about a dev pre-release? It's confusing, what is the goal trying to achieve with this post?

    And why not using semantic versioning?

     pycon
        
>>> from packaging.version import Version
>>> v = Version("0.0.1-alpha.22")
>>> str(v)
'0.0.1a22'
>>>

    0.0.1alpha22 or 0.0.1a22 although that looks alot like pre-release dev level fixes. In which case, 0.0.1a0-dev22

    There is no project ever that had 22 alpha releases. That's nuts. Your alpha testers must be really overworked.

    Fire the six year old in charge versioning decisions ;-)

    Your welcome. Your future user base can thank me later for putting a stop to that atrocity posing as versioning

    epoch is used to transition from random nonsense versioning to semantic versioning.

    There is no shame/stigma for admitting a mistake and correcting it. Eventhough that epoch will now stick around with the project forever.

  • Announcing iceoryx2 v0.7: Fast and Robust Inter-Process Communication (IPC) Library for Rust, Python, C++, and C

    Jump

  • congrats on the publishing the Python bindings. Puts it on our radar

  • Scaling asyncio on Free-Threaded Python

    Jump

  • Hip hip hooray!

  • Python Mutability

    Jump

  • AI reads github issues and crapoverflow for us cuz that is where packages are mainly documented.

    The package documentation is a historical document according to every PEP ever. ;-)

    What if github issues&discussions disappeared tomorrow? That feeling in your ballsack is what free falling feels like?

    Forever wars? np we are due for some excitement.

    github disappearing suddenly ... that keeps me awake at night

    Is Copilot unemployment in it's future?

  • Python Mutability

    Jump

  • Ah! Haven't yet reached stubborn old geezer stage.

    Don't immediately understand exactly what the code does? Must be cuz of mental slippage. Like brain plague or residual PHP or jinja2 knowhow that can't be purged.

    We all know it's not from drug use or excessive party lifestyle. Maybe excessive retro Linux gaming?

    Whatever it is, those exercises are great diagnosis tool.

  • Python Mutability

    Jump

  • First i love the visualizations. It grew on me. And supportive of coding challenges posts. As long as there isn't a flood of them. Which there isn't.

    I get your position. That there just isn't an explanation for each and every exercise. The other comments made it seemed like there was.

    When i clicked on the Explanation link, the browser didn't initially scroll to the Mutability section. Went downhill from there.

    btw i'm too dumb to know the answer and too lazy to copy+paste the code into a REPR.

    All the other commenters are just dishonest pretending they totally got it without running the code ;-)

  • Python Mutability

    Jump

  • Here is the link to the code which is being in-browser remote executed

    exercise14.py

    There is no "explanation" next to or within the file. A exercise14.rst or test_exercise14.py would be nice.

    The Explanation link provided contains a mountain of visual shit (aka noise) none of which looks like exercise14.py code.

    The OP is trying to teach us, i get that. Looks like i'm failing the (mountain of visual shit) reading comprehension section of this exercise.

  • Python Mutability

    Jump

  • Yeah and the link went to a site with in-browser remote code execution. Dodgy.

    Clicking Play or GetURL did nothing.

    Luckily my browser is as old as me. And was too grumpy to actually do what it's told.