Alyssa Coghlan

Things that need trolling: authoritarian governments, corrupt multinationals, abusive "leaders". Who do weak sycophants harass? Vocal women.

@dstufft Even figuring out a suitable *review* process for those early packaging ones was quite an extended saga!

I'm pretty sure that @ncoghlan_dev remembers how much I complained during those first couple ;)

I've apparently written or been involved in writing 20 (well technically 21) PEPs in decade-ish since I've been writing them. Does not feel like I've written that many. My list: gist.github.com/dstufft/888d97…

For anyone curious, the addition is a new "See also" block for concurrent.futures at the start of the threading docs (and a similar addition in multiprocessing): docs.python.org/3/library/thre…

The good kind of conference driven development: identified a documentation hole based on a talk, posted a PR that evening to close it. #kiwipycon

@pfctdayelise Context was that different situations will have different hierarchies. The bottom tier in this particular example was also for truly one-off code (where an Undo button is likely enough history)

The scientific hierarchy of coding needs described by @Sydonahi is honestly pretty similar to what commercial software needs (just replacing scientific impact with business/bottom line impact in guiding the investment of time) #kiwipycon

@s_lott Android recommended enough articles from them to realise they're throwing up clickbait to get outraged views (sometimes with articles on the same day arguing opposite perspectives without mentioning each other)

High praise indeed from Tom Clark at #kiwipycon: "Context managers are no more complicated than they need to be" :)

@anthonypjshaw @pyblogsal There's also a home for any CPython crashers you find that are deemed "Won't fix": github.com/python/cpython… :)

@HeyChelseaTroy @raymondh @llanga Open source living up to its goals :)

@nhumrich For the benefit of anyone else reading the Twitter thread: we chatted via DM, and rather than submit a new PEP, @nhumrich is going to look into brushing the dust and cobwebs off the existing PEP 501, and becoming a co-author on that.

Looking for a Python-core-developer to sponsor my new PEP. Its essentially a revisit of PEP 501. github.com/nhumrich/peps/… Tagging @ncoghlan_dev because of the history, but please feel free to tag others you feel might be interested.

Teachers! Just a few more days to get #pyconline student showcase applications in for @PyConAU! Have your students made something cool using python? Maybe an assignment, side project, or game? We want to hear about it! 2021.pycon.org.au/education/

@KathyReid @candeira (I write this as someone that let his passport expire for the first time in 20+ years a few months back, since you're still eligible for the fast path renewal process up to 3 years after expiry)

@KathyReid @candeira I'm picturing an Australian Passport Office group chat: Bob: Should we turn off the renewal reminder scheduled job? It's not like anyone can travel anyway. Tina: Won't that create a huge renewal backlog when the borders open again? Bob: Oh yeah, good point. I'll leave it alone.

Today, on Phishing or Sarcasm?

@nhumrich But yeah, even I never really warmed to the "i" prefix (over the original "t" prefix), and if we went back to proposing the "t" prefix we could at least borrow half of the JS terminology (template literals), even if "template strings" needed to be avoided due to "string.Template"

@nhumrich Folks also objected to calling them strings when they may never actually be rendered to a string at any point (unlike f-strings, which are eagerly rendered by the compiler), but it was the "string.Template already exists" argument that I personally found compelling.

@di_codes @MylesBorins But IIRC, the original motivation for allowing them in the PEP was just "PyPI already has projects with 4+ numeric segments in their version numbers, they're not ambiguous in any way, so there is no reason to disallow them".

@di_codes @MylesBorins The specific thing I personally use a 4th digit for is CalVer-with-patch-releases. Normal versions are YY.M.serial (to allow for multiple feature releases in the same month), if a patch series is needed for some reason, it becomes, YY.M.serial.patch.

Hey @ncoghlan_dev I'm just reading pep 440 and was curious on the reasoning for the more permissive release segment as compared to the semver spec. It just dawned on me that a version with any number of dot separated values would be valid in this spec as per N(.N)*

With the inclusion of async generator based features, the minimum supported version is now Python 3.6+, so it will be interesting to find out if anyone is still using old Python versions with old versions of installation tools that ignore the Required-Python metadata field.

Release notes at #release-history" target="_blank" rel="nofollow noopener">contextlib2.readthedocs.io/en/stable/#rel…

contextlib2 21.6.0 has been released, updating the API to match Python 3.10 (including all the previously omitted asynchronous features from 3.7+): pypi.org/project/contex…