> Did you still want this addressed? Anthony and I made some comments
> on the bug/patch, but nothing has been updated.
I was waiting because I got unassigned from the bug, so I thought
the maintainer was stepping up. I'll commit a fix for it today.
Thanks for pinging me,
--
Gustavo Niemeyer
Gustavo,
Did you still want this addressed? Anthony and I made some comments
on the bug/patch, but nothing has been updated.
n
--
On 8/15/06, Gustavo Niemeyer <[EMAIL PROTECTED]> wrote:
> > If you have issues, respond ASAP! The release candidate is planned to
> > be cut this Thursday/Friday.
"A.M. Kuchling" <[EMAIL PROTECTED]> writes:
> On Tue, Aug 15, 2006 at 10:44:40PM -0400, Kurt B. Kaiser wrote:
>> It would be nice if the key IDLE changes could make it to the "What's New
>> in Python X.X". If Andrew is interested, I could draft something for him.
>
> Sure! I can try to look thro
Neal Norwitz <[EMAIL PROTECTED]> wrote:
> On 8/15/06, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
>>
>> It would be nice if someone could bytecompile Lib using
>> Tools/compiler/compile.py and then run the test suite.
>
> Has this been done before?
Obviously not. :-)
> # This code causes python t
On Tue, Aug 15, 2006 at 10:44:40PM -0400, Kurt B. Kaiser wrote:
> It would be nice if the key IDLE changes could make it to the "What's New
> in Python X.X". If Andrew is interested, I could draft something for him.
Sure! I can try to look through the IDLE NEWS file, but you'd
certainly have a b
On 8/15/06, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
>
> It would be nice if someone could bytecompile Lib using
> Tools/compiler/compile.py and then run the test suite. I'd do it
> myself but can't spare the time at the moment (I started but ran
> into what seems to be a gcc bug along the way)
Anthony Baxter <[EMAIL PROTECTED]> writes:
> I'd also like to see idle's separate version number go away and have
> it start using the Python version number - maybe as of 2.6?
+1
When we merged IDLEfork the consensus was to keep the versioning
separate. But it seems confusing and is extra work
On Tuesday 15 August 2006 22:57, Thomas Heller wrote:
> What is the policy for documentation changes? Am I allowed to check in
> changes/additions to the ctypes docs without release manager permission
> after the release candidate is out? I'l always make sure that the html
> docs can be built.
S
I really don't care any more about this. My initial concern (and why I
requested the change) was that there are no more official separate distutils
releases. I don't see how keeping a bunch of version numbers in the stdlib
that just track the main version number is a sane use of developer time -
Neal Norwitz <[EMAIL PROTECTED]> wrote:
> I don't know of any. I haven't heard of any issues with the fixes
> that have been checked in.
It would be nice if someone could bytecompile Lib using
Tools/compiler/compile.py and then run the test suite. I'd do it
myself but can't spare the time at the
Martin v. Löwis wrote:
> M.-A. Lemburg schrieb:
>>> It's either an official feature, with somebody maintaining it,
>>> or people should expect to break it anytime.
>> I'll let you know when things break - is that good enough ?
>
> That can't be an official policy; you seem to define "breaks"
> as
M.-A. Lemburg schrieb:
>> It's either an official feature, with somebody maintaining it,
>> or people should expect to break it anytime.
>
> I'll let you know when things break - is that good enough ?
That can't be an official policy; you seem to define "breaks"
as "breaks in my (your) personal u
> If you have issues, respond ASAP! The release candidate is planned to
> be cut this Thursday/Friday. There are only a few more days before
> code freeze. A branch will be made when the release candidate is cut.
I'd like to see problem #1531862 fixed. The bug is clear and the
fix should be tr
Guido van Rossum wrote:
> Marc-Andre,
>
> I think the release managers might let you change this back if you
> volunteered, not to maintain all of distutils (I wouldn't wish that on
> my worst enemies :-) but at least to keep the version number up to
> date and to do the occasional work to keep it
Martin v. Löwis wrote:
> M.-A. Lemburg schrieb:
>> I find it important to maintain distutils compatibility with
>> a few Python versions back. Even if I can't volunteer to
>> maintain distutils, like Martin suggested, due to lack of time,
>> I don't really see the requirement to use the latest and
Marc-Andre,
I think the release managers might let you change this back if you
volunteered, not to maintain all of distutils (I wouldn't wish that on
my worst enemies :-) but at least to keep the version number up to
date and to do the occasional work to keep it backwards compatible in
the way you
Martin v. Löwis wrote:
> Guido van Rossum schrieb:
>> I think it must be rolled back, at least as long as
>> distutils is officially listed as a package that needs to support
>> older versions of Python, which pretty much implies that it's okay to
>> extract it from the 2.5 release and distribute i
M.-A. Lemburg schrieb:
> I find it important to maintain distutils compatibility with
> a few Python versions back. Even if I can't volunteer to
> maintain distutils, like Martin suggested, due to lack of time,
> I don't really see the requirement to use the latest and greatest
> Python features in
Guido van Rossum schrieb:
> I am sympathetic to this case. Is there any advantage to the *users*
> of distutils of the dynamic version number?
This series of commits was triggered by a user who wondered why
Python 2.4.3 ships with distutils 2.4.1, yet Python 2.5bsomething
ships with the older 2.4.
Guido van Rossum wrote:
> On 8/15/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
>> The distutils version number should be changed back to a static
>> string literal.
>>
>> It's currently setup to get its version number
>> from the Python version running it which pretty much defeats
>> the whole purp
On 8/15/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> The distutils version number should be changed back to a static
> string literal.
>
> It's currently setup to get its version number
> from the Python version running it which pretty much defeats
> the whole purpose of having a version number a
Neal Norwitz wrote:
> I just updated the PEP to remove all references to issues blocking
> release of 2.5.
> I don't know of any. I haven't heard of any issues with the fixes
> that have been checked in.
>
> If you have issues, respond ASAP! The release candidate is planned to
> be cut this Thur
Neal Norwitz schrieb:
> I just updated the PEP to remove all references to issues blocking
> release of 2.5.
> I don't know of any. I haven't heard of any issues with the fixes
> that have been checked in.
>
> If you have issues, respond ASAP! The release candidate is planned to
> be cut this Th
On Tuesday 15 August 2006 14:31, Neal Norwitz wrote:
> I just updated the PEP to remove all references to issues blocking
> release of 2.5.
> I don't know of any. I haven't heard of any issues with the fixes
> that have been checked in.
>
> If you have issues, respond ASAP! The release candidate
24 matches
Mail list logo
