[Python-Dev] os.access and Unicode

[M.-A. Lemburg]

Martin v. Löwis wrote:
> M.-A. Lemburg wrote:
> 
>>> The question is whether it would encourage conditional work-arounds. 
>>
>>
>>
>> -1. That only makes the code more complicated.
> 
> 
> You misunderstand. I'm not proposing that the work-around is added
> to Python. I'm saying that Python *users* might introduce such
> work-arounds to their code.

Ah, ok.

Either way, the code get's more complicated :-)

>> +1. Application writers can add tests for the correct version
>> of Python to their application and give a warning to the user
>> in case the version doesn't match.
> 
> 
> Application writers typically don't do that if they can find
> a work-around, because that means less hassle for their users.
> They accept that the code will get more complicated because
> of the work-around, and blame Python for having this bug in the
> first place.

Hmm, eGenix always suggests to people to use the latest
patch level release, esp. for production systems, not only
for Python itself, but also for the products. Zope Corp.
does the same, as do many other application writers.

The only time where we do add work-arounds is for changes
between minor Python versions in order to make the same
code base work for multiple Python versions, but that's
rare.

> In any case, I can't backport the os.access change without explicit
> permission from Anthony.

Agreed.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Mar 11 2005)
 >>> Python/Zope Consulting and Support ...        http://www.egenix.com/
 >>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::