[Python-Dev] Merry Christmas to me, and Python users everywhere
I didn't see an announcement that 3.6.0 had actually been released, but I have been longing for the ability to actually write UTF-8 strings to the console without using "ascii" or "json.dumps" to avoid the cp437 codec, and be able to write characters from other the whole Unicode repertoire. I was sitting here wishing I could better read some such output... The schedule was 23 December 2016. I decided to see if it had been released. It seems to be there on Python.org! I installed it today, which is, as far as I am concerned, still Christmas until I go to bed, which will be soon, and it is really still Christmas in Hawaii as I type this. So Merry Christmas to me, and to Python users everywhere. And I changed one of my many programs that want to print UTF-8 to the console, and it worked. I am happy. Many, many thanks to Steve Dower, who actually pushed the PEPs into the release, as well as all the other people that have been involved in incremental reports, workarounds, and ideas throughout the course of Issue1602. And congratulations to everyone on a successful release. Glenn ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PySlice_GetIndicesEx annd stable ABI: bikeshedding
On 21.12.16 19:34, Brett Cannon wrote: On Wed, 21 Dec 2016 at 06:52 Serhiy Storchaka mailto:storch...@gmail.com>> wrote: [SNIP] Let's start bikeshedding. What are your ideas about names and the order of arguments of two following functions? 1. Takes a slice object, returns it's start, stop and step as Py_ssize_t values. Can fail. start, stop, step 2. Takes slice's start, stop, step, and the length of the sequence (all are Py_ssize_t), returns adjusted start, stop, and the length of sliced subsequence (as Py_ssize_t). Always success. length, start, stop, step No specific ideas on names. Thank you for your response Brett. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Merry Christmas to me, and Python users everywhere
On 12/26/2016 1:25 AM, Glenn Linderman wrote: I didn't see an announcement that 3.6.0 had actually been released Off list, Burkhard Meier helped me figure out why I hadn't seen the announcement: It was sent as one email cross-posted to multiple groups. I am subscribed to 3 of those groups: python-announce, python-list, python-dev with this same email address. My mail filter rules would have seen the many To: address, and filtered /all/ copies I received to the python-list mailbox, because my filter rules looked for python-list before python-dev. I've just changed that to give priority to python-dev before the others. (just one of the evil side-effects of cross-posting!) But, as far as I can tell, I only received one message, and that went to the wrong folder first... the one where python-list should go. In reviewing my filters, I was reminded that python-announce and python-dev go to the same folder, which I read regularly. The python-list folder I can't keep up with, I read it occasionally, and search it when I have questions -- using it as a locally stored resource of helpful tips, and that is where the announcement went, because of the order of my filter rules, and the cross-posted announcement. So either Google (my email host) noticed that I got 3 of the same message, and suppressed two of them, or the python-dev mail server that hosts the mailing lists merged the expanded destinations with duplicate suppression. I'm inclined to think the former is more likely. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
