Re: [Python-Dev] Workflow improvement PEPs 474 & 462 updated

2015-02-01 Thread Nick Coghlan
On 2 Feb 2015 04:56, "francis" wrote: > > Hi Nick, > > On 02/01/2015 08:46 AM, Nick Coghlan wrote: > [...] > > The updates to PEP 462, which covers proposed changes to the main > > CPython workflow, were more significant, as I've now rewritten that to > > depend on PEP 474, and propose replacing t

Re: [Python-Dev] PEP 484 syntax: NONONONONONONO!

2015-02-01 Thread Chris Angelico
On Sun, Feb 1, 2015 at 9:13 PM, Benjamin wrote: > I much prefer the idea of a 'where' keyword to denote typing, as discussed > http://aroberge.blogspot.com/2015/01/type-hinting-in-python-focus-on.html, > but I think a refinement of their idea would prove even better: > > def retry(callback, timeou

Re: [Python-Dev] Workflow improvement PEPs 474 & 462 updated

2015-02-01 Thread francis
Hi Nick, On 02/01/2015 08:46 AM, Nick Coghlan wrote: [...] > The updates to PEP 462, which covers proposed changes to the main > CPython workflow, were more significant, as I've now rewritten that to > depend on PEP 474, and propose replacing the current Rietveld patch > review workflow with an up

Re: [Python-Dev] PEP 484 syntax: NONONONONONONO!

2015-02-01 Thread Mark Lawrence
On 01/02/2015 10:13, Benjamin wrote: The proposed syntax is abominable. It's the opposite of readable. I have no views on the subject as I won't be using it, but there is no need to shout to get your point across. -- My fellow Pythonistas, ask not what our language can do for you, ask what

[Python-Dev] PEP 484 syntax: NONONONONONONO!

2015-02-01 Thread Benjamin
The proposed syntax is abominable. It's the opposite of readable. The function annotation syntax is ugly, but potentially useful for things like documentation. While it may very well have been created with the idea of type-checking, actually using it for such quickly turns into an unreadable moras

Re: [Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-02-01 Thread Ryan Gonzalez
That looks better! Looks like now the real encoding issues are coming up. Try going to line 269 of pythonrun.c and changing: PyErr_SetNone(PyExc_NotImplementedError); return NULL; to: char* m = malloc(6); strcpy(m, "ascii"); return m; This just sets a default encoding. On Sat, Jan 31, 2015 at

Re: [Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-02-01 Thread Ryan
Ok...try this (based on http://dan.drown.org/android/howto/gdb.html): - Install BusyBox and a Terminal Emulator - Inside the Terminal Emulator, run: su cd /data/local/tmp wget http://dan.drown.org/android/gdb- static.tar.gz tar zxf gdb-static.tar.gz ./gdb Now, inside gdb, type: set

Re: [Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-02-01 Thread Cyd Haselton
Ergh...this may not work. I've already got BusyBox and a terminal installed, but the python build...and all other utilities that I use...are running in a fakechrooted environment inside the terminal. That environment only filters dynamic calls to libc, so the statically compiled gdb won't work i

Re: [Python-Dev] Newly Built Python3 Binary Throws Segfault

2015-02-01 Thread Cyd Haselton
Very interesting. I got this error Fatal Python error: Py_Initialize: Unable to get the locale encoding NotImplementedError Aborted generate-posix-vars failed make: *** [pybuilddir.txt] Error 1 ...but it didn't (of course) segfault. I'll pull gdb, get the results and send them. On January 31,