Files are immutable on PyPI, releases are not (because releases are comprised of a set of files, and files are uploaded one by one).
This is unintuitive, but the TL;DR is that files will never change on PyPI, but (previously) a user could upload a new file to a release years after their last upload to that release. This has some legitimate use cases (like allowing people to support new Python versions without bumping a package’s version), but also makes introduces challenges around locking and release security that are elaborated in the thread linked by the blog post.
I agree this could probably be ratcheted down from 14 days over time, though.
Worth noting, because I think it’s confusing some folks on this comments page, that “file” here is “a wheel for a platform” or “a complete sdist”, not “each individual .py file in a release”
You can’t go back later and add “evil.py” to a bunch of existing release files, but you could previously go find a bunch of releases that didn’t have arm64 files, publish malicious ones, and use that to catch people using those versions on arm64 systems
It doesn’t. It’s really only relevant if you use version-specific APIs/ABIs in wheels containing machine code. Pure Python wheels don’t generally need this.
[ Header ][ ...variable padding... ][ Back Pointer ][ User Memory ]
^ always exactly sizeof(void*)
bytes before User Memory,
no matter how much padding
came before it
and then it says we don't need to align the back pointer and we end up with
[ Header ][ Back Pointer ][ Padding ][ User Memory ]
without a clear explanation of how we now get to the back pointer if it's behind the variable alignment.
I started using it because me and my flatmate had different media libraries and we wanted to share them. Plex very conveniently merged both into a single deduplicated library that we could pick from when watching something on the TV.
The author lost me at the last bit where they started using weird names for the posts. Why would you make one ID O and the other ID 0? Why single letters and not EMBED_01? Why seemingly random letters instead of ABCDEF? Does OCPDST stand for something?
They are placeholders, their meanings are spelled out in the post:
O: publish/oembed_cache, empty content, stale timestamp with parent C
C: future/customize_changeset, changeset JSON with parent C
P: draft/page, with parent D
D: parse/request with itself as its parent
S: publish/post, for providing embed data
T: publish/post, containing the outer embed
canals have negligible water flow (except during disasters!) so I don't think that'd work very well. They also get dredged occasionally so there's a decent chance anything you leave down there won't last more than a couple of years
Depends on the canal. The UK narrow boat network has locked everywhere so minimal current in most sections similarly the Netherlands. In fact most canals. But then you have something like Suez which is just open to the ocean.
The UK locks themselves are water movement though, so if you wanted to power something for "free" on those, you'd attach it to there. Oh man did I love watching those as a kid. You wouldn't do a fan though, you'd have a line and a buoy and use the up and down motion to drive a linear electromagnetic generator to harvest energy.
I don't have the magazine to verify, but wikipedia says
> In 2005, Retro Gamer called Snes9x "the best SNES emulator available".[12]
If there was a Retro Gamer magazine writing about SNES emulators, I think it's safe to say some people did consider even the SNES to be retro, 14 years after its US release. My personal experience having used Snes9x around that time, we also considered it retro.
Clearly not everyone though, which is my point in saying what's retro will depend on who you ask.
By 2006 when the PS3 came 'round, the NES was definitely retro. It wasn't a livingroom staple anymore, and examples that survived were well-loved (either in the wear-and-tear way, in the appreciation-of-objects way, or both).
The NES was only ~21 years old at the time that the PS3 came out.
It was very surprising for me when I visited the US to see just how much space was wasted writing everything out on every sign and sometimes in giant words on the road.
It did also make me a bit worried about the expected level of driver education...
To me it's odd to imply people must be stupid because they're expected to read a few simple words such as "Left lane must turn left" rather than to memorize a bunch of symbols.
American signs very frequently combine both styles - for instance, you see the above words next to a sign with arrows for whatever lanes, wordlessly illustrating the turn types permitted.
If someone is a new driver, who hasn't seen the symbolic signs enough, the word signs are a good fallback. The goal is to maximize accessibility.
The system of signs used is an independent question from the level of driver education (which probably is generally lower in the USA than in most European countries though), which also is another question from whether people "are stupid".
The obvious benefit of the European style is that you don't need to speak the language in order to understand the signs, something that is clearly less important given the relative homogeneity of language in the USA.
But at least to me, the European road signs are also more quick to read. For example, the "only right turns" and "speed limit 60" are exactly the same shape and color in the USA, while in Europe there is more of a logical system (which also means you don't "memorize a bunch of symbols", you learn the "language" of the signs), such as blue disc means "mandatory", red circle means "prohibited", red triangle means "warning", etc.
People have seen the symbols since childhood, and as far as I know in every European country it's necessary to pass the exam on knowing what they mean before starting practical driving lessons.
Driving in Europe would be completely impossible without them. I have no idea what the Greek word for "no parking or stopping between 09 and 15" is, or the Croatian word for "left".
I agree - to me, that is the main practical reason Europe is a special case well-suited to symbolic signs.
The US doesn't have nearly that issue, since we have tons of symbolic signs, and few languages, which share a ton of close cognates anyway. For instance, most Mexicans I've heard will use the verb "parquear" or "aparcar" to mean "to park" rather than "estacionar" - so as you might expect, they have zero trouble decoding a sign saying "NO PARKING 9AM - 6PM" which is one of the most complicated text-only signs you usually see.
I didn't say they were stupid, I said I was concerned about their level of education
> If someone is a new driver, who hasn't seen the symbolic signs enough, the word signs are a good fallback. The goal is to maximize accessibility.
That's the thing I'm concerned about! In Europe you're not allowed onto the road unless you have already proven that you have memorised all the symbols and can identify them on demand. You don't need to maximise accessibility because the required level of education is higher.
>It did also make me a bit worried about the expected level of driver education...
Not just driver, but of the general population. A few decades ago, the general reading level was at the 6th grade (thanks to the policies of Ronald Regan) and republicans think that is too high and have been working intensely to lower it. Won't be surprised if it's dropped given the "golden" opportunity of covid. I know it's only been a few years (centuries for most Americans) since Betsy DeVos was secretary of education. Remember that era?
reply