Hi Nitin,
Thanks for your interest in CPython for Google Summer of Code.
We are still getting our ducks in a row, and mentor organizations haven't
been finalized yet (the official mentor list will go out on February 24th).
Can you check back in then?
In the meantime, I recommend:
1. Joining htt
Thanks for your reply.
I have joined on the pythonmentors.com and gone through the developer
guide.
Yes, I am going through the present bugs to resolve some of them.
Could you Please reply as soon as you get the mentors allocated for the
Possible
email projects being proposed for Gsoc 2014. It w
29.01.14 20:24, Serhiy Storchaka написав(ла):
The Py_CLEAR macros is used as safe alternative for following unsafe
idiomatic code:
Py_XDECREF(ptr);
ptr = NULL;
But other unsafe idiomatic code is widely used in the sources:
Py_XDECREF(ptr);
ptr = new_value;
Every occurrence
Many Python tests were written a very long time before the unittest,
using simple asserts. Then, when they have been ported to the unittest,
asserts were replaced with the assert_ method and then with assertTrue.
The unittest has a number of other methods to check for and report
failure, from a
How Enum items should be pickled, by value or by name?
I think that Enum will be used to collect system-depending constants, so
the value of AddressFamily.AF_UNIX can be 1 on one platform and 2 on
other. If pickle enums by value, then pickled AddressFamily.AF_INET on
on platform can be unpickl
On Sat, Feb 15, 2014, at 10:12 AM, Serhiy Storchaka wrote:
> Many Python tests were written a very long time before the unittest,
> using simple asserts. Then, when they have been ported to the unittest,
> asserts were replaced with the assert_ method and then with assertTrue.
> The unittest has
On Sat, 15 Feb 2014 21:01:36 +0200
Serhiy Storchaka wrote:
> How Enum items should be pickled, by value or by name?
>
> I think that Enum will be used to collect system-depending constants, so
> the value of AddressFamily.AF_UNIX can be 1 on one platform and 2 on
> other. If pickle enums by val
On 2/15/2014 1:12 PM, Serhiy Storchaka wrote:
Many Python tests were written a very long time before the unittest,
using simple asserts. Then, when they have been ported to the unittest,
asserts were replaced with the assert_ method and then with assertTrue.
The unittest has a number of other met
On 13 February 2014 20:58, Paul Moore wrote:
> On 13 February 2014 20:54, Donald Stufft wrote:
>>
>> On Feb 13, 2014, at 3:53 PM, Paul Moore wrote:
>>
>>> Can someone please take a look at http://bugs.python.org/issue20621
>>> for me? It appears that there is a significant problem with zipimport
In article
<1392492250.26338.83831085.39a5e...@webmail.messagingengine.com>,
Benjamin Peterson wrote:
> On Sat, Feb 15, 2014, at 10:12 AM, Serhiy Storchaka wrote:
> > Although Raymond approved a patch for test_bigmem [2], his expressed the
> > insistent recommendation not to do this. So I stop
On 16 February 2014 02:52, Serhiy Storchaka wrote:
> There are objections to these patches. Raymond against backporting the patch
> unless some known bugs are being fixed [1]. But it fixes at least one bug
> that caused a crash. And I suspect that there may be other bugs, just we
> still have no r
On 16 February 2014 09:20, Ned Deily wrote:
> In article
> <1392492250.26338.83831085.39a5e...@webmail.messagingengine.com>,
> Benjamin Peterson wrote:
>> On Sat, Feb 15, 2014, at 10:12 AM, Serhiy Storchaka wrote:
>> > Although Raymond approved a patch for test_bigmem [2], his expressed the
>> >
12 matches
Mail list logo
