On Thu, Nov 8, 2012 at 10:56 AM, Steven D'Aprano
wrote:
> On Thu, 08 Nov 2012 10:14:35 +1100, Chris Angelico wrote:
>
>> On Thu, Nov 8, 2012 at 5:35 AM, anatoly techtonik
>> wrote:
>>> I thought of sys.py3k check ...
>
> Chris, you regularly reply to the wrong mailing list, and you've just
> done
On Thu, 08 Nov 2012 10:14:35 +1100, Chris Angelico wrote:
> On Thu, Nov 8, 2012 at 5:35 AM, anatoly techtonik
> wrote:
>> I thought of sys.py3k check ...
Chris, you regularly reply to the wrong mailing list, and you've just
done it again. This is not python-ideas.
--
Steven
--
http://mail.
On Thu, Nov 8, 2012 at 5:35 AM, anatoly techtonik wrote:
> I thought of sys.py3k check as an explicit way to guard the code that should
> be maintained extra carefully for Python 3 compatibility, so that you can
> grep the source for this constant and remove all the hacks (such as bytes to
> strin
On Mon, Nov 5, 2012 at 9:33 AM, Steven D'Aprano wrote:
> On 05/11/12 08:49, anatoly techtonik wrote:
>>
>> if sys.py3k:
>># some py2k specific code
>>pass
>
> # Bring back reload in Python 3.
> try:
> reload
> except NameError:
> from imp import reload
>
> try:
> any
> except N
