[Pyrex] [Cython] ANN: Pyrex 0.9.8

[Kirill Smelkov]

В сообщении от Пятница 16 мая 2008 Greg Ewing написал(a):
> Kirill Smelkov wrote:
> 
> > Greg, I'd like to ask you about
> > 
> >   Why don't you host normal Mercurial repository for Pyrex?
> 
> For a number of reasons, it wouldn't be convenient for me
> to have the definitive repository on a remote site.
> 
> I'm open to the idea of having a mirror site somewhere
> that is kept up to date, although I don't have anywhere
> to put one at the moment.

Greg, I see your points.

Yes, please, let's have Pyrex mirror somewhere. Today I've noticed this is
already setup at

http://hg.cython.org/pyrex/

So, I think everyone would be grateful to you if you'll keep it up-to-date.


As to your wish to keep the definitive repository at your side, I'd like to
say that as I understand, usually distributed development works in the
following way:

People, clone your repository, make their improvements and send patches back to
maintainer (in Pyrex case this is you).

So then the maintainer could see if a patch is ok, or wrong, or semi-ok and
needs more work, etc.

This is all general terms, and of course one could do the same based on Pyrex-x.y.z.tar.gz,

but everything is easier and more convenient, if the main repository is
visible to all.

And you know, sometimes it positively affects development ...

> In the meantime, I'm making Mercurial bundles available
> to anyone who wants to maintain their own repository.

This are all appreciated steps in positive direction, thanks!

> Something I'd like to point out is that there isn't
> usually any "bleeding edge" that's significantly
> different from the last released version. I have bursts
> of working on Pyrex, and any changes I make almost
> always turn up as a new release very soon after I've
> made them. It's not as if I'm sitting on things for
> months before releasing them, if that's what anyone
> is thinking.

I see.

I respect you very much as Pyrex language designer and creator, and I'm *very*
thankful to you because I was fascinated by the idea when I first saw it, and
when I used Pyrex I had *very* positive experience.

So BIG "THANK YOU, GREG!"

But look, isn't there is no bleeding edge because mainly *you* work on it?

Greg, everything, somehow someday *have* to become team work because one
person can't scale that much.

Just look at it: Python has a bunch of core development guys and PEPS

Why don't we do the same? Yes I know, it could be somewhat scary and
uncomfortable to let others to play in not-trivial way with your baby,
but this just has to be done, sooner or later!

You say you still design Pyrex as a language, but look at your recent quote
taken from http://article.gmane.org/gmane.comp.python.cython.devel/1642

> What I'd really like to do is make new-style division be
> on all the time, but in light of the recent integer for-loop
> fiasco, I'm reluctant to do anything that might break old
> code.

So Pyrex is already took off, and we have to gradually improve it and care not
to break existing deployments as well. This is not a one-man task.

So why can't we do it all together?!

Yes, you'll loose precise control on what Pyrex is, but given there is a shell of
motivated people around, I think Pyrex and you will gain much more in return ...

That's how I think ...
Please let me know *your* thoughts.

Thanks,
Kirill.