Show newer

@offby1 I've got some vague hopes for this: arewep2pyet.com/

I'm thinking 5% chance it will happen, but it would be cool if it did.

I'm translating an figure for a article. I have an alignment problem due to the being not available everywhere. Is there a way to right-align text boxes independently of the actual font being used? I want them to remain editable as text. I'm using .

This is the file's page: commons.wikimedia.org/wiki/Fil
In my browser (Chrome on Ubuntu), the text is misaligned (image 1). Image 2 is the screenshot of the relevant SVG code.

From what I can gather, text-anchor:end is indeed what we want to ensure right-alignment but it's not working. Any idea on how to make this work?

I kinda thought Amazon was just completely neglecting Goodreads, but they've recently been doing a bunch of messing around with the front-end in a very "likes are now florps / timeline goes sideways" way.

Show thread

Possibly this is related to the fact that Goodreads is the *slowest website I use regularly*, and has been for many, many years?

Show thread

Goodreads, I've regularly used your website for *13 years*, and reviewed over 1000 books. I've got librarian privileges and I'm not even using a bunch of weird IP addresses.

Why do I need to complete a captcha every time I submit a review?

@tonwood Qoto also has a bunch of nice to have features like **markdown** and quote tweets, plus the very roomy 65k character limit.

Python packaging 

@pradyunsg Yeah, when I deploy PyPy a bunch of stuff builds from source, including SqlAlchemy. `backports.zoneinfo` also has no PyPy wheels because it is not possible to specify that a wheel is a generic PyPy wheel (see: github.com/pypa/packaging/issu )

I suspect there's low coverage for PyPy because of some combination of PyPy being a different beast, people not wanting a combinatorial explosion on their CI builds and people just not bothering.

Python packaging 

@pradyunsg I'm pretty sure this would be *massively* disruptive to anyone using pypy.

New post:

harihareswara.net/posts/2022/s

I've started regularly using OpenAI's #Whisper to make transcripts and captions/subtitles, and am writing to share how, and why, and my reflections on the ethics of using it.

A lot of HOWTO in here, but the last section dives into @simon's #ML #machinelearning #AI vegan analogy in a way you might find interesting even if Whisper isn't your thing.

When you're doing walking lunges next to someone doing high steps and another person doing lateral band walks.

I’m happy to announce #Python attrs 22.2.0!

The headline feature is certainly the `alias` argument to fields that allows you to freely set the __init__ name for attributes (e.g. if you don't like attrs's behavior of stripping underscore).

But there's also a lot of under-the-hood improvements around performance and typing.

This is the last version to support Python 3.6. 🫡

github.com/python-attrs/attrs/

@xarvos @gforsyth @tacaswell @tomasino I don't think that's going to solve any of the problems around semver-based pinning.

@gforsyth @tacaswell FWIW while you are loosening pins it looks like you upper pin like... all your dependencies, which is a recipe for disaster in the long run. See, e.g.: iscinumpy.gitlab.io/post/bound

I'm guessing this is a side effect of using poetry: iscinumpy.dev/post/poetry-vers

Should You Use Upper Bound Version Constraints?

Bound version constraints (upper caps) are starting to show up in the Python ecosystem. This is causing real world problems with libraries following this recommendation, and is likely to continue to get worse; this practice does not scale to large numbers of libraries or large numbers of users. In this discussion I would like to explain why always providing an upper limit causes far more harm than good even for true SemVer libraries, why libraries that pin upper limits require more frequent updates rather than less, and why it is not scalable. After reading this, hopefully you will always consider every cap you add, you will know the (few) places where pinning an upper limit is reasonable, and will possibly even avoid using libraries that pin upper limits needlessly until the author updates them to remove these pins. If this 10,000 word behemoth is a bit long for you, then skip around using the table of contents, or see the TL;DR section at the end, or read version numbers by Bernát Gábor, which is shorter but is a fantastic read with good examples and cute dog pictures. Or Hynek’s Semantic Versioning Will Not Save You Be sure to check at least the JavaScript project analysis before you leave! Also be warned, I pick on Poetry quite a bit. The rising popularity of Poetry is likely due to the simplicity of having one tool vs. many for packaging, but it happens to also have a special dependency solver, a new upper bound syntax, and a strong recommendation to always limit upper versions - in direct opposition to members of the Python core developer team and PyPA developers. Not all libraries with excessive version capping are Poetry projects (like TensorFlow), but many, many of them are. To be clear, Poetry doesn’t force version pinning on you, but it does push you really, really hard to always version cap, and it’s targeting new Python users that don’t know any better yet than to accept bad recommendations. And these affect the whole ecosystem, including users who do not use poetry, but want to depend on libraries that do! I do really like other aspects of Poetry, and would like to eventually help it build binary packages with Scikit-build (CMake) via a plugin, and I use it on some of my projects happily. If I don’t pick on Poetry enough for you, don’t worry, I have a follow-up post that picks on it in much more detail. Also, check out pdm, which gives many of the benefits of Poetry while following PEP standards.

iscinumpy.gitlab.io

Just stumbled across my 7th grade school transcripts. Apparently I got an F in Technology, so I think that means a career as a programmer isn't going to work out.

On the plus side, I got an A- in Latin, so I guess it's Vale programming, Salve... being a Latin teacher?

Coverage.py 7.0 has shipped!

The feature change is `report --format`, but the version bumped because you might need to fix some settings.

Let me know if something is truly broken!
pypi.org/project/coverage/7.0.

Looks like #Coverage 7 for #python dropped and here's a pro tip:

If you had:

```
[tool.coverage.paths]
source = ["src", ".tox/*/site-packages"]
```

change the second line to:

```
source = ["src", ".tox/**/site-packages"]
```

(or even `source = ["src", ".tox/py*/**/site-packages"]`)

If nothing about this makes sense: hynek.me/articles/testing-pack

meta snark 

@hynek @glyph I'm legitimately tempted to start such an instance just so I can mute it.

Plus side is I can probably raise $3.5M at a $4B valuation to do it.

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.