(Hopefully) the future of network protocols in Python
Back in February I started taking a serious look at asynchronous I/O thanks to
await. One of the things that led to me to looking into this area was when I couldn't find an HTTP/1.1 library that worked with
await. A little surprised by this, I went looking for an HTTP header parser so that I could do the asynchronous I/O . . .
Or, geez is proper security a pain!
Why the hell do I care about security?
Bad people exist out there; it sucks, but there it is. That means you need to take precautionary measures to make sure that bad people can't get at your stuff. In terms of your online stuff, that means passwords. Lots of passwords. Lost of sufficiently complex passwords. Lots and lots of sufficiently . . .
Or, implicit compatibility is usually not a good thing
Over on python-ideas a discussion has broken out about somehow trying to make
p'/some/path/to/a/file return an instance of
pathlib.Path. This led to a splinter discussion as to why
pathlib.Path doesn't inherit from
str? I figured instead of burying my response to this question in the thread I'd blog about it to try and explain one . . .
Or, the business case for moving to Python 3
[This blog post has been sitting as a draft for months, and I'm finally finishing while at home sick; sorry if that makes it a little less coherent compared to my other posts]
Or, generators let you do neat stuff
Being a core developer of Python has made me want to understand how the language generally works. I realize there will always be obscure corners where I don't know every intricate detail, but to be able to help with issues and the general design of Python I feel like I should try and understand its core semantics and how things work under . . .
Or, why it took over a year for me to make a decision
I asked on Twitter if people would be interested in having me write down the history behind my decision to choose GitHub for Python's future development process and people said "yes"(some literally), hence this blog post.
Posted in: python
It's a new calendar year, which means it's time to think about what year-long plans I have for my contributions to the Python project. There's always the usual plans I have to approve some patches, fix some bugs, etc. But I seem to always have one or two projects that I really want to see happen that I simply can't solve in a . . .
Posted in: python
Cover image credit: http://goo.gl/photos/re3FDeopYikjWfbK8