Re: [EVALUATION] - E02 - Support for MinGW Open Source Compiler

From: Ilias Lazaridis (ilias_at_lazaridis.com)
Date: 02/20/05 

Date: Sun, 20 Feb 2005 18:20:33 +0200

Martin v. Löwis wrote:
> Ilias Lazaridis wrote:
>
>> Should I take answers serious?
>
> If not, why are you asking questions in the first place?

simply read the next question, which limits the scope of the first one.

>> Answer from people which do not respect coherence of writings?
>
> Coherence of writings?

An example:

they above 2 questions are coherent, thus answering isolated [as you've
done] makes not much sense.

"
>> Should I take answers serious?
>> Answer from people which do not respect coherence of writings?
"

[answering here makes sense]

>> Should a professional developer take python serious?
>
> Yes.
>
>> I mean, if the team does not manage at least the foundation of a
>> multi-target automated-build-process?
>
> If the team *would* not manage at least the foundation of a
> multi-target automated-build-process, a professional developer
> *should* not take python serious.

Very nice.

At this point, we agree very much.

> However, since the team *does* manage at least the foundation of
> a multi-target automated-build-process, a professional developer
> *might* take python serious.

here our disagreement:

=> {"managing the foundation of a multi-target automated-build-process"}

What are the requirements for fulfilling this?

> [a false premise can imply anything]

again you ignore coherent writings.

-

You have omitted the following part of my writings:

"[targets need not to be supported directly by the python team. They
could be added/managed/maintained by community members]"

in which I essentially define a few requirements for "managing the
foundation of a multi-target automated-build-process".

-

The python team should provide the fundamental infrastructure for the
community, thus it can add/manage/maintain build targets.

Additionally:
   * The python-team should detect any efforts made for different
build-targets
   * The python-team should attract/engourage the authors to include
them in the main build-system [incubation section].

The python-community and the PSF supports the python-team to take the
above actions.

> Regards,
> Martin

. 

-- 
http://lazaridis.com

Relevant Pages

  • Re: On Whose Desktop
    ... Leung, Dino Viehland (core developer of IronPython), Titus Brown, Ivan ... Any women in Python you could ask - how about Anna Ravenscroft? ... I hope *everyone* knows that Martin was the winner of this year's Frank ...
    (comp.lang.python)
  • Re: undefined symbol: PyUnicodeUCS4_FromUnicode
    ... When I removed the python stuff in /usr ... Martin v. Löwis wrote: ... > Bill Hodges wrote: ... >> Python then compiled to UCS4 ...
    (comp.lang.python)
  • Re: using mmap on large (> 2 Gig) files
    ... this is a known limitation of Python 2.4: ... NumPy uses the mmap object and I saw a paper at SciPy 2006 that used Python 2.5 + mmap + numpy to do some pretty nice and relatively fast manipulations of very large data sets. ... the very useful changes by Martin have seen more testing than he is probably aware of. ...
    (comp.lang.python)
  • Re: Tremendous slowdown due to garbage collection
    ... Martin said that the default settings for the cyclic gc works for most ... typical for common application but typical for an artificial benchmark. ... Python is optimized for regular apps, not for benchmark (like some video ... much less memory - and memory Python 2.5 and older will never release ...
    (comp.lang.python)
  • Re: [EVALUATION] - E02 - Support for MinGW Open Source Compiler
    ... >>Should a professional developer take python serious? ... - (ungentle babbling after disrupting coherence of writings) ... [targets need not to be supported directly by the python team. ...
    (comp.lang.python)