diazona

diazona, 2 months ago

@moira I wouldn't say no to some space kaiju though

#Monsterdon

diazona, 2 months ago

@jonny Personally I think it made a decent amount of sense, it just had enough other problems to make up for it

Super weird regardless

#Monsterdon

diazona, 2 months ago

@jonny Well yeah the last 10 minutes were a real curveball for sure, but other than that I actually thought it made a fair bit of sense. Like, not that everything was explained, but there was a coherent plot, and most of the events of the movie contributed to advancing that plot.

#Monsterdon

diazona, 2 months ago

@Canageek @jonny Yeah that bit was just weird

#Monsterdon

diazona, 2 months ago

@RomanOnARiver Probably depends on what you're doing with them?

I guess the RAM usage would likely be more with multiple lists, although probably not much more. But other than that it could be context-dependent.

#Python #programming

diazona, 2 months ago

@aldi80s What are the key features you're looking for? (or not looking for? ie why didn't you like about #Bookwyrm)

#books #bookstodon

diazona, 2 months ago

@aldi80s Makes sense. I wonder if it's a problem with the Bookwyrm software or with the server? Because in the latter case, maybe you could try making an account on a different server and it would do better.

Other than that, I don't know if anything else quite compares to the social features of Bookwyrm. I see someone else recommended The Story Graph, which I use and it's pretty good, but it does have a different set of priorities.

diazona, 2 months ago

@glyph what am I looking at 😂

diazona, 2 months ago

@glyph haha definitely 👍

diazona, 2 months ago

@fohrloop Huh. I did a quick experiment which suggests otherwise:

>>> from packaging.version import Version
>>> from packaging.specifiers import SpecifierSet
>>> s1 = SpecifierSet("==2.2.0")
>>> Version("2.2.0.post0") in s1
False
>>> Version("2.2.0.post1") in s1
False
>>> Version("2.2.0") in s1
True

(".post0" is the canonical way of writing "-0", and so on)

#Python #PythonSecurity #security #pip

diazona, 2 months ago

@fohrloop Ahh, I see: the "1" is actually a "build tag" as per the wheel naming spec https://packaging.python.org/en/latest/specifications/binary-distribution-format/#binary-distribution-format.

So yeah, this is confusing: you can actually have a version 2.2.0-1, which is equivalent to 2.2.0.post1, and if that were the case, pip would be able to tell the difference. But the 2.2.0-1 mentioned in the video and your original toot is not a version, it's a part of the wheel filename, and it actually means version 2.2.0 with build tag 1, which is something different.

#Python

diazona, 2 months ago

@hugovk @fohrloop Yeah I think that was mentioned somewhere earlier, but personally I'd rather just use a separate post release to solve that problem. IMO it's too unintuitive that you can install the same version of a package on the same system and get different code.

#Python

diazona, 2 months ago

@hugovk @fohrloop Agreed, except for pointing people to the /latest/ RTD page; I think it's very reasonable to decide not to do that in general.

Anyway, I would say updating the documentation is a perfect opportunity to make a post release.

#Python

diazona, 2 months ago

@fohrloop @hugovk For a very small project this can work okay, but only if you change the tag quickly enough that nobody notices. In general, I think a better approach is to use release candidates: when you think you're ready to make a release, prepare it as an rc first and then after you've given yourself and others time to check it for possible issues, then retag the rc as the final version and release that. Then it should be quite rare that you need to change something after making the final release without incrementing the version number. But in the rare instances where you do, then I think having it show up as X.Y.Z.post1 in RTD is fine.

#Python

diazona, 2 months ago

@fohrloop @hugovk Oh I was assuming that /latest/ points to the documentation of the last commit on your main development branch, while /stable/ points to the documentation of the latest released version (i.e. with a version number). So, people who download the project from /pypi/ will more likely want the /stable/ version.

diazona, 2 months ago

@hugovk @fohrloop Well... I acknowledge your point, but given the way things are moving toward reproducibility these days, I think it's really valuable to have a deterministic mapping between (package, version, system) and wheel. That is, given the constraint that I want to install a particular version of a particular package on a particular system, there should be one specific wheel file that will be used for that particular installation. If a wheel file is broken or something, then I think making a new version needs to be the price of fixing that. (If that involves pinging people in some way that's annoying, then I would say it's the notification system that should be fixed.)

diazona, 2 months ago

@hugovk @fohrloop Indeed!

I never heard of Sigstore but I will have to check that out, thanks 😀

diazona, 2 months ago

@moira The cross? I thought crosses work

#Monsterdon

diazona, 2 months ago

@moira ooooh this makes a lot of sense

So I wonder if an aluminum mirror would work?

Or a digital camera?

#Monsterdon

diazona, 2 months ago

@AkaSci Oh nice, this thread will be a good starting point to update my list! (https://www.ellipsix.net/arxiv-joke-papers.html)

#arxiv #arXivFools

diazona, 2 months ago

@geofft @glyph @eb I'm certainly not disputing that it's a real problem that that doesn't happen more often, but isn't there some precedent for big tech companies hiring people to work on specific open source projects? So it's not totally unheard of

diazona, 2 months ago

@glyph @geofft @eb Oh of course. I guess I just wanted to acknowledge being in a state of "a tiny bit of progress" rather than "zero progress". (I have an optimistic streak that comes out sometimes)

diazona, 2 months ago

@dalias @geofft @glyph @luis_in_brief @eb Legally speaking I think it could be set up either way. Although if an OSS project maintainer is employed (not contracted) by a company to maintain the project, it is kind of as if the company is acting as the maintainer, which certainly raises questions about their motivation....

diazona, 2 months ago

@eb @glyph Very cool! Any chance you might be willing to share that particular snippet - even just the HTML structure - under a less restrictive license than AGPL? It seems like the kind of thing I would love to use or adapt on my own site, but I don't want to (and probably legally can't) share my site and all the services it uses under that license.

diazona, 2 months ago

@meejah @jacob Yeah for sure. This is actually something I personally really like about Git, that when I mess up I basically always have a route to undo it, and I often don't find that to be true with systems that are simpler and more user-friendly.