Gregor Lingl wrote:
> Yes,, and I have some ideas in this respect, but mainly a prioncipal
> question. I read about
> using doctest and unittest, but how does one devise
> automatic test suites for graphical output. In the end it depends on how
> it looks like.
There are a few options here.. Tw
Gregor Lingl wrote:
> One question in this respect - how important do you consider
> backward compatibility. When designing a new module the requirement
> backward copmpatibility can have a big impact on the code although it
> may in some parts be questionable. As an example let me mention the
> r
Martin v. Löwis schrieb:
> Gregor Lingl wrote:
>
> ...
>> (Who reviewed it? This is a _newly_added_ function -
>> did nobody try it out yet? Incredible!!)
>>
>
> Apparently not. Thanks for pointing that out; Georg (who committed the
> patch originally) just fixed it in r47151.
>
> This illu
Gregor Lingl wrote:
> So, if you can't accept that offer - now, or even ever - , because it
> contradicts your rules, that's o.k. But it's not 'my cause'. I
> concieve it to be the community's cause.
All "we" said is that we cannot integrate it now, as a policy matter.
Nobody said it can't be in
On 6/28/06, Gregor Lingl <[EMAIL PROTECTED]> wrote:
> I made xturtle.py and that was a big effort. And I offer it to replace
> turtle.py. I do this because I'm a Python enthusiast and I want a better
> Python. (And I know very well that my contribution is rather marginal).
> We all, I think, have t
Fredrik Lundh schrieb:
> Gregor Lingl wrote:
>
>
>> What a shame!! An immanent bug, persistent
>> for years now!
>>
>> Is this what Anthony Baxter calls
>> "the most solid Python release ever"
>>
>
> do you really think stuff like this helps your cause ?
>
>
Perhaps it dosn't help the tu
Guido van Rossum wrote:
> It was already patched by the other Georg. Thanks for the quick fix, georgbot!
My pleasure, even if there's a difference between "Georg" and "Gregor" ;)
cheers,
Georg
___
Python-Dev mailing list
Python-Dev@python.org
http://ma
Gregor Lingl wrote:
> For example: put turtle.py and xturtle.py both into beta2 and
> see which one stands better the (beta)test of time. Or perhaps you have
> an even better idea!
As a compromise, we could put an ad into the turtle document (a "see
also" link).
Regards,
Martin
_
Gregor Lingl wrote:
> Sorry Martin, but to me this seems not to be the right way to manage
> things.
As you explain later, this is precisely the right way; it is unfortunate
that it isn't always followed.
> (Who reviewed it? This is a _newly_added_ function -
> did nobody try it out yet? Incredib
It was already patched by the other Georg. Thanks for the quick fix, georgbot!
--Guido
On 6/28/06, Bob Ippolito <[EMAIL PROTECTED]> wrote:
>
> On Jun 28, 2006, at 1:05 PM, Gregor Lingl wrote:
>
> > Martin v. Löwis schrieb:
> >> Collin Winter wrote:
> >>
> >>> While I have no opinion on Gregor's a
On Jun 28, 2006, at 1:05 PM, Gregor Lingl wrote:
> Martin v. Löwis schrieb:
>> Collin Winter wrote:
>>
>>> While I have no opinion on Gregor's app, and while I fully agree
>>> that
>>> new language features and stdlib modules should generally stay
>>> out of
>>> bug-fix point releases, xturtl
Gregor Lingl wrote:
> What a shame!! An immanent bug, persistent
> for years now!
>
> Is this what Anthony Baxter calls
> "the most solid Python release ever"
do you really think stuff like this helps your cause ?
___
Python-Dev mailing list
Python-
Martin v. Löwis schrieb:
Collin Winter wrote:
While I have no opinion on Gregor's app, and while I fully agree that
new language features and stdlib modules should generally stay out of
bug-fix point releases, xturtle doesn't seem to rise to that level
(and hence, those restrictions).
13 matches
Mail list logo
