Nick Coghlan gmail.com> writes:
>
> On Tue, Jun 28, 2011 at 1:09 AM, renaud gmail.com> wrote:
> > Nick Coghlan gmail.com> writes:
> >
> >> I hit a snag with this. The real tests of the PEP 380 functionality
> >> aren't currently part of the patch - they're a big set of "golden
> >> output" tes
On Tue, Jun 28, 2011 at 1:09 AM, renaud wrote:
> Nick Coghlan gmail.com> writes:
>
>> I hit a snag with this. The real tests of the PEP 380 functionality
>> aren't currently part of the patch - they're a big set of "golden
>> output" tests in the zipfile hosted on Greg's site. Those need to be
>>
Nick Coghlan gmail.com> writes:
> I hit a snag with this. The real tests of the PEP 380 functionality
> aren't currently part of the patch - they're a big set of "golden
> output" tests in the zipfile hosted on Greg's site. Those need to be
> refactored into proper unittest or doctest based addit
On Sun, Jun 26, 2011 at 1:16 PM, Nick Coghlan wrote:
> On Sun, Jun 26, 2011 at 2:44 AM, Guido van Rossum wrote:
>> Let me cut this short. PEP 380 is pretty much approved. I know there
>> are a few details worth quibbling over, but they are not going to
>> jeopardize acceptance of the PEP. We are
On Sun, Jun 26, 2011 at 2:44 AM, Guido van Rossum wrote:
> Let me cut this short. PEP 380 is pretty much approved. I know there
> are a few details worth quibbling over, but they are not going to
> jeopardize acceptance of the PEP. We are waiting for an implementation
> in Python 3.3. In fact, I w
