Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <python-python-list@m.gmane.org>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.048
X-Spam-Evidence: '*H*': 0.90; '*S*': 0.00; 'classes.': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'commented': 0.16; 'new-style': 0.16; 'old-style': 0.16; 'presume': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'sign.': 0.16; 'subject:proxy': 0.16; 'wrote:': 0.18; 'module': 0.19; 'header:User-Agent:1': 0.23; '2.1': 0.24; '2.x': 0.24; 'subject:problem': 0.24; 'updating': 0.26; 'header:X -Complaints-To:1': 0.27; 'header:In-Reply-To:1': 0.27; 'code': 0.31; 'class': 0.32; 'compatible': 0.32; 'classes': 0.35; 'but': 0.35; 'version': 0.36; 'functions.': 0.36; 'transition': 0.36; 'done': 0.36; 'thanks': 0.36; 'changing': 0.37; 'being': 0.38; 'remote': 0.38; 'to:addr:python-list': 0.38; 'explain': 0.39; 'skip:. 10': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'how': 0.40; 'analysis,': 0.60; 'lost': 0.61; 'first': 0.61; 'you.': 0.62; 'more': 0.64; 'here': 0.66; 'below.': 0.71; 'received:109': 0.72; 'cut': 0.74; 'guides': 0.74; 'behavior': 0.77; 'abandoning': 0.84; 'presumably': 0.84; 'magical': 0.91
X-Injected-Via-Gmane: http://gmane.org/
To: python-list@python.org
From: Robin Becker <robin@reportlab.com>
Subject: Re: reporting proxy porting problem
Date: Mon, 02 Dec 2013 14:42:52 +0000
References: <5297250A.80709@chamonix.reportlab.co.uk> <l78efk$lv3$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gmane-NNTP-Posting-Host: 109.174.168.73
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
In-Reply-To: <l78efk$lv3$1@ger.gmane.org>
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.3463.1385995385.18130.python-list@python.org>
Lines: 35
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1385995385 news.xs4all.nl 15947 [2001:888:2000:d::a6]:50713
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:60869

On 28/11/2013 22:01, Terry Reedy wrote:
..............
>
> All the transition guides I have seen recommend first updating 2.x code (and its
> tests) to work in 2.x with *all* classes being new-style classes. I presume one
> of the code checker programs will check this for you. To some extent, the
> upgrade can be done by changing one class at a time.
>

the intent is to produce a compatible code with aid of six.py like functions.


> Yes, this means abandoning support of 2.1 ;-). It also means giving up
> magical hacks that only work with old-style classes.
>
>> I find that I don't understand exactly how the original works so well,
>
> To me, not being comprehensible is not a good sign. I explain some of
> the behavior below.

The author has commented that he might have been drunk at time of writing :)


>
>> but here is a cut down version
>
..

thanks for the analysis, I think we came to the same broad conclusion. I think 
this particular module may get lost in the wash. If it ever needs 
re-implementing we can presumably rely on some more general approach as used in 
the various remote object proxies like pyro or similar.
-- 
Robin Becker