[issue5052] Mark distutils to stay compatible with 2.3

[Tarek Ziadé]

Tarek Ziadé  added the comment:

Ok, I will rewrite the top README file to explain this (and PEP 291 as
well) and keep the Python 2.3 compatibility in the whole package.

--
status: closed -> open
title: "This module should be kept compatible with Python 2.1." in distutils 
code -> Mark distutils to stay compatible with 2.3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5052] Mark distutils to stay compatible with 2.3

[Akira Kitada]

Akira Kitada  added the comment:

Is there any PEP describing we have to keep compatibility with 2.3 
release? I'm not against the idea but just curious.

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5052] Mark distutils to stay compatible with 2.3

[Marc-Andre Lemburg]

Marc-Andre Lemburg  added the comment:

Some more explanation for why keeping distutils Python 2.3 compatible is
desirable:

distutils was removed from the PEP without any public discussion outside
a sprint at PyCon and the reasons given for it did not take into account
that people will want to use a single distutils version (that of the
lastest released Python version) to build packages for multiple Python
versions.

distutils in Python 2.6 no longer works with Python 2.1, but it still
does mostly with Python 2.3 and I would prefer to have to use that
version as minimum required.

Over the years I've always tried to rework any changes that were done
which did not meet that requirement and only left non-Python 2.3 code
in place that was not relevant for that version anyway, e.g. the
new MSVC code for Python 2.6.

Please also note that distutils is not a performance critical piece of
software. Making it more developer friendly to extending via
sub-classing and more user friendly by adding more support for platform
specific installer format is much more important than using the latest
and greatest tricks in Python.

With Python 2.7 released, we can then move on to Python 2.4
compatibility and so on.

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5052] Mark distutils to stay compatible with 2.3

[Tarek Ziadé]

Tarek Ziadé  added the comment:

ok the current trunk won't run even under 2.5...

I will make two small changes:

- use md5 module of haslib is not found
- make the smallest possible change for site.USER_BASE 
  and site.USER_SITE usage

--
nosy: +christian.heimes

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5052] Mark distutils to stay compatible with 2.3

[Tarek Ziadé]

Changes by Tarek Ziadé :


--
keywords: +patch
Added file: http://bugs.python.org/file13197/2.3.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5052] Mark distutils to stay compatible with 2.3

[Tarek Ziadé]

Tarek Ziadé  added the comment:

And we're back in PEP 291 !

see r70019, r70017 and r70021

--
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com