Arc, at this point all I ever hear from you is how Cython is so horrible and has to be rewritten to be even tolerable. What exactly is so horrible about Cython? You have never given any specifics on why Cython is so horrible that it is better to start from scratch and thus violate about every good rule of programming (see Joel on Software). If this isn't intended to be FUD why don't you name some specific features that require a full rewrite as opposed to making grand movements, which are in many cases flat out wrong, that seem designed only to attack Cython and Pyrex? Are you actually going to produce code at some point? Last I heard there was some grand plan to fork Cython and license it under GPL3 that went predictably nowhere. Why are you taking on an even grander project? If your goal is to produce a simple graphics engine why are you getting into the compiler business?
On Sat, May 10, 2008 at 9:54 PM, Arc Riley <[EMAIL PROTECTED]> wrote: >> I just read our FAQ and it does not say that. > > "The intention is to make it a drop-in replacement for existing Pyrex code." > > If this is not the meaning you intended, then you may want to change > the way the FAQ reads. > > >> I wrote "fork" because that's exactly how you describe >> PyMill on the Pymill trac server page: http://pysoy.org:8000/ >> That page disappeared so I can't paste from it. > > That "page" is a development tracd that is not open to the public and > nothing on it is official in any way. The numerous broken images on > it should have been a clue, if the port wasn't enough. Your reposting > it here was the reason it was moved to another port. > > The reason we're not using the name "PyMill" in any public posting is > that may not even be the name we end up with. There's a good chance > it isn't. We're nowhere near the point of publishing a definition of > it. You'll notice my blog entry didn't use the name. > > In fact your entire panic mode seems to be derived from a warped sense > of importance of a posting to our internal development list a link you > followed from it to a draft site we're working from. Nothing you > pasted, besides a link to the blog entry, was read by the general > Python community until you posted it here. > > Again - if there's something in the blog posting that is inaccurate, > specify it, and I'll correct it. That is the only referenced place > where FUD (sic) could have been spread, since everything else was > internal. > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev > _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
