On Thu, Nov 12, 2009 at 7:34 AM, David Cournapeau
<da...@ar.media.kyoto-u.ac.jp> wrote:
[...]
>   - existing usage of distutils API should remain compatible. I asked
> in a previous email what is meant by distutils API, Tarek answered
> anything which does not start with an underscore. But what does that
> mean ? For example, in numscons, I rely on the build directory to have a
> certain structure (implemented defined in distutils: you can't retrieve
> them from distutils from public API). Is this part of the API ? Is using
> copied commands to get some characteristics considered part of the API ?
> Is the order of commands, or their attributes considered public (they
> all start without an underscore, but they are not documented anywhere) ?

The build and instalation scheme should be part of the API. If you
look in sysconfig,
you get most of the install schemes via the API. If anything is
missing, tell us.

Now for the build I am not sure what you are trying to perform here.
I'll ask you
for a precise example here.

But are you willing to do this finish the discussion of this precise example ?
I mean, if I give you an answer, *or* a proposal for a change in Distutils,
is your answer is going to be "distutils must be replaced anyway" ?
or are you willing to hear my proposal and work it out with me ?

Because, Distutils is not going to be replaced.


[..]
>
> During a more precise discussion, I think we have more or less agreed
> with Tarek that build_ext needs a significant overhaul. Although we did
> not discuss concretely about other commands, I think the same kind of
> arguments apply to almost any command. There is then the issue of
> communicating between commands, through the Distribution class.

And I made a proposal for this last one too in this thread.  But, like
the Extensions proposal I have made,
you seem not to hear them.

I don't get it. It seems to me that you just don't want to see
Distutils improved, since
everytime you mention a problem, and I start to make proposals, we
don't discuss it further and you jump
back on the 'distutils must be replaced' line.

But what is going to happen is that,  Distutils will not be replaced.
We want to make it evolve.

[..]
> Python distutils (the one included in python) has broken our extensions
> countless times already, even though no significant feature has been
> added.

Sorry, but that's pretty vague. Are you mentioning the changes in
build_ext, or something else ?


Tarek.
_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig

Reply via email to