On 14 Nov 2013 10:40, "christian.heimes" wrote:
>
> http://hg.python.org/cpython/rev/99ba1772c469
> changeset: 87089:99ba1772c469
> user:Christian Heimes
> date:Thu Nov 14 01:39:35 2013 +0100
> summary:
> Issue #17828: va_start() must be accompanied by va_end()
> CID 1128793:
On Wed, Nov 13, 2013 at 2:48 PM, Christian Heimes wrote:
> Am 13.11.2013 23:37, schrieb Eli Bendersky:
> > Yeah, it definitely could. There are two problems currently: 1) the
> > patches are for 2.7.x and 2) they have some ugly hacks in them. But I
> > will talk to the guy who worked on that and h
Am 13.11.2013 23:37, schrieb Eli Bendersky:
> Yeah, it definitely could. There are two problems currently: 1) the
> patches are for 2.7.x and 2) they have some ugly hacks in them. But I
> will talk to the guy who worked on that and hopefully we'll be able to
> have something cleaned up for upstream
On Wed, Nov 13, 2013 at 10:27 AM, Brett Cannon wrote:
>
>
>
> On Wed, Nov 13, 2013 at 1:05 PM, Eli Bendersky wrote:
>
>>
>>
>>
>> On Wed, Nov 13, 2013 at 6:58 AM, Brett Cannon wrote:
>>
>>>
>>>
>>>
>>> On Wed, Nov 13, 2013 at 6:30 AM, Facundo Batista <
>>> facundobati...@gmail.com> wrote:
>>>
>
On Wed, Nov 13, 2013 at 1:05 PM, Eli Bendersky wrote:
>
>
>
> On Wed, Nov 13, 2013 at 6:58 AM, Brett Cannon wrote:
>
>>
>>
>>
>> On Wed, Nov 13, 2013 at 6:30 AM, Facundo Batista <
>> facundobati...@gmail.com> wrote:
>>
>>> On Wed, Nov 13, 2013 at 4:37 AM, Maciej Fijalkowski
>>> wrote:
>>>
>>> >
On Wed, Nov 13, 2013 at 6:58 AM, Brett Cannon wrote:
>
>
>
> On Wed, Nov 13, 2013 at 6:30 AM, Facundo Batista > wrote:
>
>> On Wed, Nov 13, 2013 at 4:37 AM, Maciej Fijalkowski
>> wrote:
>>
>> >> Do you think it would be productive to create an independent Python
>> >> compiler, designed with sa
On 14 November 2013 01:43, Stephen J. Turnbull wrote:
> Nick Coghlan writes:
>
> > The long gory history in http://bugs.python.org/issue7475 took a
> > different turn earlier this year when I noticed
> > (http://bugs.python.org/issue7475#msg187698) that the codecs module
> > already *had* type
On 14 November 2013 02:12, Nick Coghlan wrote:
> On 14 November 2013 00:30, Walter Dörwald wrote:
>> On 13.11.13 14:51, nick.coghlan wrote:
>>
>>> http://hg.python.org/cpython/rev/854a2cea31b9
>>> changeset: 87084:854a2cea31b9
>>> user:Nick Coghlan
>>> date:Wed Nov 13 23:49:21
On 14 November 2013 00:30, Walter Dörwald wrote:
> On 13.11.13 14:51, nick.coghlan wrote:
>
>> http://hg.python.org/cpython/rev/854a2cea31b9
>> changeset: 87084:854a2cea31b9
>> user:Nick Coghlan
>> date:Wed Nov 13 23:49:21 2013 +1000
>> summary:
>>Close #17828: better handli
Nick Coghlan writes:
> The long gory history in http://bugs.python.org/issue7475 took a
> different turn earlier this year when I noticed
> (http://bugs.python.org/issue7475#msg187698) that the codecs module
> already *had* type neutral helper functions in the form of
> codecs.encode and code
On 13/11/2013 09:33, Simon Cross wrote:
Thanks for writing this email. It's well written and it takes a lot of
character to stand up and say you went down the wrong road. While I'm
here - thanks also for all your work on core Python. As a Python user
I really appreciate it.
Schiavo
Simon
Big
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/13/2013 01:54 AM, Nick Coghlan wrote:
> I actually applaud his decision to post his final conclusion to the
> list, even though it wasn't the outcome he was hoping for. Negative
> data is still data :)
Amen! I also applaud the work he put into
On Wed, Nov 13, 2013 at 6:30 AM, Facundo Batista
wrote:
> On Wed, Nov 13, 2013 at 4:37 AM, Maciej Fijalkowski
> wrote:
>
> >> Do you think it would be productive to create an independent Python
> >> compiler, designed with sandboxing in mind from the beginning?
> >
> > PyPy sandbox does work FYI
On 13.11.13 14:51, nick.coghlan wrote:
http://hg.python.org/cpython/rev/854a2cea31b9
changeset: 87084:854a2cea31b9
user:Nick Coghlan
date:Wed Nov 13 23:49:21 2013 +1000
summary:
Close #17828: better handling of codec errors
- output type errors now redirect users to the ty
On 13.11.2013 15:29, Nick Coghlan wrote:
> Back in Python 3.2, the non-Unicode codecs were restored to the
> standard library, but without the associated aliases (mostly due to
> some thoroughly confusing error messages when they were mistakenly
> used with the Unicode encoding convenience methods)
Back in Python 3.2, the non-Unicode codecs were restored to the
standard library, but without the associated aliases (mostly due to
some thoroughly confusing error messages when they were mistakenly
used with the Unicode encoding convenience methods).
The long gory history in http://bugs.python.or
On 13 November 2013 08:52, Victor Stinner wrote:
> Hi Giampaolo,
>
> You forgot to update tests after your change in repr(socket). Tests
> are failing on buildbots, just one example:
>
> ==
> FAIL: test_repr (test.test_socket.Gene
On Wed, Nov 13, 2013 at 4:37 AM, Maciej Fijalkowski wrote:
>> Do you think it would be productive to create an independent Python
>> compiler, designed with sandboxing in mind from the beginning?
>
> PyPy sandbox does work FYI
>
> It might not do exactly what you want, but it both provides a full
Thanks for writing this email. It's well written and it takes a lot of
character to stand up and say you went down the wrong road. While I'm
here - thanks also for all your work on core Python. As a Python user
I really appreciate it.
Schiavo
Simon
___
P
2013/11/13 Glenn Linderman :
> If it is an implementation issue, then perhaps a different implementation
> would help. Or perhaps a "safe compiler".
There is PyPy with its sandbox.
> If it is a language design issue, then a different implementation wouldn't
> help, it would require a new language
20 matches
Mail list logo
