Lisandro Dalcin wrote:
>> 2) Should all the package names be converted to lowercase?
>
> Perhaps we should follow PEP 8 ?
Sure. When we break stuff, make sure we only have to do it once. That also
includes asking on python-dev what a suitable target package would be for
the stdlib.
>> 3) Should one perhaps distribute Cython under two seperate package
>> names, so that a standalone version can coexist with the one in stdlib?
>> This would facilitate easy installation and usage of non-stdlib Cython
>> releases. Can't come up with any good names though.
>
> 1) cython
> 2) cython.core
> 3) cython.pyximport
Yes, one package for everything. So, what you mean is: rename the current
Cython package to "cython.core"? Would that be for the stdlib or for the
external package?
> Regarding (1), I would make it have in the cython/__init__.py define
> __version__,
Sure.
> and also have cython/run.py for cmd line work with -m
> switch, and make __init__py use that for newer Python versions that
> let you run packages.
Note that those aren't that "new" anymore. What do people think about
dropping the "cython" frontend alltogether, and making
python -m cython
the official way to start the Cython compiler? I doubt that there are still
a lot of developers who do not have access to Python 2.4 or later in one
way or another. And not being able to run Cython in Python 2.3 wouldn't
hurt anyone either, I guess, as long as the generated code keeps compiling.
> cython/__init__.py should also manage the shadow stuff
Which it already does now.
Stefan
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev
