Steven Bethard wrote:
> On Wed, Mar 19, 2008 at 5:51 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>> This flag is exposed to python code as sys.flags.py3k_warning
>>
>> So the hack added to some of the test code that I saw go by on
>> python-checkins isn't needed :)
>
> Excellent. I asked around
On Wed, Mar 19, 2008 at 5:51 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> This flag is exposed to python code as sys.flags.py3k_warning
>
> So the hack added to some of the test code that I saw go by on
> python-checkins isn't needed :)
Excellent. I asked around at the sprints and everyone tho
On Wed, Mar 19, 2008 at 6:51 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> This flag is exposed to python code as sys.flags.py3k_warning
>
> So the hack added to some of the test code that I saw go by on
> python-checkins isn't needed :)
Somebody can remove TODO in Lib/test/test_py3kwarn.py.
>
>
This flag is exposed to python code as sys.flags.py3k_warning
So the hack added to some of the test code that I saw go by on
python-checkins isn't needed :)
Cheers,
Nick
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
--