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
9
Comments
331
Joined
2 yr. ago

  • Linux backlash leads to California law change on age verification - with the original lawmaker forced to make a humbling step back

    Jump

  • Faintly heard someone say, show me the source code, so here it is. This is Tully's coffee captive portal wifi router "Agreement page" (my terminology).

    <div data-pagetype="step1" class="l-content"> <div class="l-main"> <div class="information-area"> <div class="inner"> <h2> <span>A simple 2STEP</span> process to use<br> <span>60minutes</span>of free WI-FI. </h2> <p class="hint">※Authentication page will be shown again when usable time has exceeded.</p> </div> </div> <div class="outer"> <form class="l-form inner"> <h4>Please give a response.<small>（Select）</small></h4> <div class="form-list"> <div class="form-item form-half"> <label>Birth Year</label> <div class="l-select"><div> <select class="placeholder"> <option disabled="disabled" hidden="hidden" value="select" selected="selected">Select</option> <option value="2026">2026Year</option> <option value="2025">2025Year</option> <option value="2024">2024Year</option> <option value="2023">2023Year</option> <option value="2022">2022Year</option> <option value="2021">2021Year</option> <option value="2020">2020Year</option> <option value="2019">2019Year</option> <option value="2018">2018Year</option> <option value="2017">2017Year</option> <option value="2016">2016Year</option> <option value="2015">2015Year</option> <option value="2014">2014Year</option> <option value="2013">2013Year</option> <option value="2012">2012Year</option> <option value="2011">2011Year</option> <option value="2010">2010Year</option> <option value="2009">2009Year</option> <option value="2008">2008Year</option> <option value="2007">2007Year</option> <option value="2006">2006Year</option> <option value="2005">2005Year</option> <option value="2004">2004Year</option> <option value="2003">2003Year</option> <option value="2002">2002Year</option> <option value="2001">2001Year</option> <option value="2000">2000Year</option> <option value="1999">1999Year</option> <option value="1998">1998Year</option> <option value="1997">1997Year</option> <option value="1996">1996Year</option> <option value="1995">1995Year</option> <option value="1994">1994Year</option> <option value="1993">1993Year</option> <option value="1992">1992Year</option> <option value="1991">1991Year</option> <option value="1990">1990Year</option> <option value="1989">1989Year</option> <option value="1988">1988Year</option> <option value="1987">1987Year</option> <option value="1986">1986Year</option> <option value="1985">1985Year</option> <option value="1984">1984Year</option> <option value="1983">1983Year</option> <option value="1982">1982Year</option> <option value="1981">1981Year</option> <option value="1980">1980Year</option> <option value="1979">1979Year</option> <option value="1978">1978Year</option> <option value="1977">1977Year</option> <option value="1976">1976Year</option> <option value="1975">1975Year</option> <option value="1974">1974Year</option> <option value="1973">1973Year</option> <option value="1972">1972Year</option> <option value="1971">1971Year</option> <option value="1970">1970Year</option> <option value="1969">1969Year</option> <option value="1968">1968Year</option> <option value="1967">1967Year</option> <option value="1966">1966Year</option> <option value="1965">1965Year</option> <option value="1964">1964Year</option> <option value="1963">1963Year</option> <option value="1962">1962Year</option> <option value="1961">1961Year</option> <option value="1960">1960Year</option> <option value="1959">1959Year</option> <option value="1958">1958Year</option> <option value="1957">1957Year</option> <option value="1956">1956Year</option> <option value="1955">1955Year</option> <option value="1954">1954Year</option> <option value="1953">1953Year</option> <option value="1952">1952Year</option> <option value="1951">1951Year</option> <option value="1950">1950Year</option> <option value="1949">1949Year</option> <option value="1948">1948Year</option> <option value="1947">1947Year</option> <option value="1946">1946Year</option> </select> </div> </div> </div> <div class="form-item form-half"> <label>Gender</label> <div class="l-select"> <div> <select class="placeholder"> <option disabled="disabled" hidden="hidden" value="select" selected="selected">Select</option> <option value="male">Male</option> <option value="female">Female</option> <option value="etc">N/A</option> </select> </div> </div> </div> </div> <div class="form-list"> <button type="submit"><span>Continue to proceed</span></button> </div> </form> </div>

  • NSFW

    types-strictyaml 1.7.3.0

    Jump

  • Unless related to AI there is no funding. A lowly stubs package is in fact not safe for work and definitely not safe on a resume, can't discuss it with your wife, friends, or in public. Even the testsuite is a freak of nature.

    Can anyone even open the github repo without contracting a social stigma?

  • NSFW

    types-strictyaml 1.7.3.0

    Jump

  • This community users don't post much cause we are lazy and shy. And posters are faced by us holding up a mirror. Most flee. Their own reflections being either too pathetic or hideous for them to defend.

    This discourages posters that lack thick skins or who are unprepared for fight club.

    Everyone is welcome to hold my feet to the fire. Don't pull your punches. Review the source code, discuss, post issues, and create PRs. Building out the testsuite is a rich target. Like shooting fish in a barrel. Only those who don't shoot, miss.

  • NSFW

    types-strictyaml 1.7.3.0

    Jump

  • Coders are easily lead astray. That checkbox called out to me with it's seductive clickability and deceptively plain design. What it lacks in esthetics it makes up for in mystery. What does NSFW mean? Thought it meant no sex for whitey.

    And for the Captain Obvious amongst us, my point is the UI lacks clarity leaving room for interpretation. Without that clarity, i'm as right as you are.

    Very much doubt anyone will get laid with the release of a stubs package. So the tag is appropriate.

    What matters is the excuse is somewhat plausible.

  • Linux backlash leads to California law change on age verification - with the original lawmaker forced to make a humbling step back

    Jump

  • Absolutely no one is fooled; especially within Linux community.

    There is always an excuse. At this point, why bother even reading the excuse. Any excuse is a childish joke and not worthy of even being entertained.

    Whichever coders grabbed their ankles should be forever ostracized.

    systemd is persona non grata.

  • Linux backlash leads to California law change on age verification - with the original lawmaker forced to make a humbling step back

    Jump

  • linux is not exempted. Open your eyes and survey some cafes access points. They have rolled out captive portals everywhere. Linux runs most routers and some variant of BSD runs the rest.

    These are the lawmakers main target. Cuz corporations can't wait to comply with edicts.

  • Interview with the Engineer of Uruky, a Private Search Engine

    Jump

  • Thank you for providing a testimonial on your experience running a searx node.

    Will revisit running a node instead of relying on the worthless public nodes.

  • Interview with the Engineer of Uruky, a Private Search Engine

    Jump

  • Since AI came on the scene, search engine result aggregators, such as searx.space, have been blocked. The UX is now laughable and unusable.

    So why are we even discussing another search engine result aggregator. What kinda difference or expectation are we supposed to have?

    As far as can tell, the choices are: AI or AI. Choose!

  • Why aren't more people using Codeberg or something open source

    Jump

  • Your reason for not moving over to forgejo is the exact same reason i'm still on github.

    So basically just shot down your own argument.

    The truth is overrated. Next time, lie thru you teeth.

    Already have that on the todo list and the transition will be completed in the next few months.

    No one would have blinked had you said that.

  • Question for People Familiar with Sphinx Documentation

    Jump

  • Life is too short for ‘sphinx.ext.todo’. It's overrated. Won't have enough hours in the day to hunt within in-code documentation for explanation of things you need to do.

    Your todo list should be in ur CHANGES.rst file. Won't be building the docs just to see todo list.

    Also the moment you have an idea, you immediately write it into CHANGES.rst. Don't wait even one second. Absolutely immediately or as soon as you get home, first thing! Write your idea first, no reading your other ideas. It'll distract you and might cause you to forget.

    Don't even think of making any code changes without writing the idea down first.

  • Question for People Familiar with Sphinx Documentation

    Jump

  • i wrote sphinx-external-toc-strict, which is a safer sphinx-external-toc. So i'm competent in Sphinx docs.

    • docs/ folder

    Follow /u/GrumpyBike1020 advise and move the docs/ out of src/ and into the project base folder.

    • venv

    Create two venv .doc/.venv and .venv. Assuming you're using pyenv, create .doc/.python-version and .venv/.python-version and .tox/.python-version. Add these to your .gitignore.

    • requirements management

    Your requirements management is overly simplistic. Do yourself a favor and use wreck to manage multiple venv requirements.

    pyproject.toml configuration

    Copy tox-req.ini into your project base folder.

    • in docs/

    reference docs/conf.py

    add this docs/Makefile modify as needed.

    Here is an example docs/_toc.yml modify for your needs.

    add this rtd config and be aware of the Python version must match Python version in tox.ini. You will forget this, it'll bite you in the ass, then you'll learn this lesson good and hard. Just come to terms that you will make this mistake.

    You are gonna have to get really good at using intersphinx inventories. The docs/Makefile will lessen the learning curve.

    The front page of your site is docs/index.rst, Create folder: docs/code. This is the root folder of your in-code documentation.

    I would like to rename it to “Source Files”

    No you don't. No table of contents in the history of time had a root named, Source files. In the TOC, you'll have a bunch of articles and a code/ folder.

    When you have questions, i'm always paying attention to this community. Just post a question will be sure to see it. Don't forget to provide your projects github repo url. Explain your issue and ask me to fix it. I'll create an GH issue with the proposed change. You have to give me the go ahead before i'll do any coding leading to a PR. I need your assurances that the change meets your approval before starting.

  • A tool for concealing writing style to evade linguistic fingerprinting

    Jump

  • Tox is only necessary if you want to validate across specific versions so it can be replaced by tools like Poetry.

    No it can't. They are two different things. tox can be replaced with nox. In the past, nox was promoted in this community. Looked into it and couldn't, for the life of me, figure out how it added value?

    You mentioned Poetry, so i get to belittle Poetry. If you hadn't mentioned it, Would have keep my mouth shut. So this is on you!

    Poetry only reason for being is to bring all the requirements files into TOML. The author loves TOML format. I get it. But at the expense of removing the constraint and requirement files hierarchy. Or a sane way of dealing with requirements of multiple venv. Or a sane clean way of managing dependency imposed lowerbound pins. Which come and go, so need to attribute which dependency imposed which set of lowerbound pins and most importantly why! Over time, the why is lost and with all the pins imposed by from various now unknown dependencies mixed into one insane pot.

    Poetry is fine if you are the author of one package (and live in a utopia and not clownworld or fight club). And you have one venv. Lets scale that up to being the prolific author or maintainer of 10 or 100 inter-dependent packages each package having multiple venv. Now you are good and fck'ed cuz Poetry doesn't handle that situation. In fact, nothing does.

    wreck tracks requirements by venv and syncs all the requirements as best it can. My intention was to eventually sync across multiple packages. But never got around to writing that level.

    Poetry is unnecessary from the day the author first sat down to write it. And is the source of frustration to end users cuz Poetry encourages author/maintainers to create dependency upperbound pins.

    So tell me again how wonderful Poetry is. Go on defend it!

  • A tool for concealing writing style to evade linguistic fingerprinting

    Jump

  • Anyway, packaging wise, you are alluding to a very real critical issue. The LLM is not packaged along with the Python code. It's just some stupid module level constant.

    That was such an obvious noob mistake, didn't even bother mentioning it. It's the elephant in the room. Amongst a herd of other problems.

    This along with the lack of, well just about everything, makes me wonder when it's time to pen an article and post it to this community.

    I say this script falls well below that mark. Whatever that mark is.

  • A tool for concealing writing style to evade linguistic fingerprinting

    Jump

  • ` And then import this project as an existing project into Eclipse (or clone and import directly within Eclipse if you have the Eclipse eGit plugin).

    This is currently the only ready way to compile and run Anonymouth. We will be including a updated build file soon so that you may build and run Anonymouth easily within the command land, but sadly it hasn't been done yet so this is the only option currently `

    What about for non-Java coders. I don't even use an IDE.

  • A tool for concealing writing style to evade linguistic fingerprinting

    Jump

  • The pyproject.toml spec is ten years old. Python 3 is almost twenty years old.

    To my knowledge, for TOML spec, strict validating against a schema is not a thing. So it's not used with very likely dangerous user input.

    So the spec could be 100,000 years old, for obvious security vulnerability reasons, would still not touch it.

    Recommend taking a read through the strictyaml authors documentation on shortcomings of various user supplied input file formats.

    You are in for a treat:

    specifically Why not TOML

  • A tool for concealing writing style to evade linguistic fingerprinting

    Jump

  • Static typing redundancy is a waste of compute.

    Have never encountered anyone suggesting doing less static type checking.

    Static typing finds bugs. Especially pyright. Especially within tests. Separating the static type checking into stubs reduces any performance impact from typing related imports.

    With py315, there will be soft|lazy import. Excess imports will have minimal impact cuz import proxy will be created but not executed until the import is actually used..

  • A tool for concealing writing style to evade linguistic fingerprinting

    Jump

  • Thank you for introducing me to act. First time seeing it.

  • A tool for concealing writing style to evade linguistic fingerprinting

    Jump

  • First thank you for taking a look and holding my feet to the fire.

    Have several packages based on strictyaml. What matters is YAML files are validated against a schema. Whether use .yml or .yaml is personal preference. My personal preference is typing less characters. Both should be allowed.

    Share your hatred of Windows and don't even see it as a serious OS. So was actually surprised that .yml has some association with Windows or MSFT.

    If while using any of below packages, you find the .yaml suffix is not recognized, that would be a bug. In which case, create an issue.

    These published packages could be affected:

    logging-strict

    pytest-logging-strict

    sphinx-external-toc-strict

    To actually confirm has bug status, would have to review the unit tests and see if .yaml is not tested nor recognized. Otherwise it's mere conjecture. It's an unconfirmed possibility. Maybe you are right, maybe not. Or maybe you are on to something.

  • A tool for concealing writing style to evade linguistic fingerprinting

    Jump

  • That sounds like a feature request.

    Create an issue

    Or don't, inwhich case it's a passive aggressive way of asking, where in duh uck are the tests?

  • Python @programming.dev
    logging_strict @programming.dev

    Criminal mind vs OSD #2

  • Python @programming.dev
    logging_strict @programming.dev

    the guy in charge of random data base object names

    github.com /fastapi/sqlmodel/issues/264
  • Programming Horror @programming.dev
    logging_strict @programming.dev

    duck hunting

  • Python @programming.dev
    logging_strict @programming.dev

    Dependency management

    pypi.org /project/wreck
  • Python @programming.dev
    logging_strict @programming.dev

    Feedback on gh profile design

    github.com /msftcangoblowm/
  • Python @programming.dev
    logging_strict @programming.dev

    Whats in a Python tarball

  • Python @programming.dev
    logging_strict @programming.dev

    PEP 735 does dependency group solve anything?

    peps.python.org /pep-0735/
  • Python @programming.dev
    logging_strict @programming.dev

    constraint vs requirement. What's the difference?