headers
Robert Bradshaw | 1 Apr 2009 01:38
Favicon

Re: [Cython] Package names

On Mar 31, 2009, at 1:48 PM, Lisandro Dalcin wrote:

> On Tue, Mar 31, 2009 at 3:17 PM, Stefan Behnel  
> <stefan_ml@...> wrote:
>>
>> 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.

+1

>>>> 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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Bradshaw | 1 Apr 2009 01:46
Favicon

Re: [Cython] Naive build system

On Mar 31, 2009, at 8:20 AM, Nicolas Dumazet wrote:

> 2009/4/1 Nicolas Dumazet <nicdumz@...>:
>> I looked at ways to avoid the extra setup.py work, it seems  
>> there's no
>> "easy way" here.
>> I thought about extending the distutils build command to build the c
>> files before the module build, but it's definitely not simple: if the
>> C files are correctly generated, one would need to register the C
>> extensions on the fly, once the build process has already started;  
>> and
>> I'm not sure that this is possible.
>> And yes, if it is not possible, one would need to write a complex
>> build system handling the whole compilation chain.
>
> Or... the setup.py behavior could be modified:
> When --no-cython-compile is not provided, if the system is not able to
> generate the .c, it bails out, spitting out an error, instead of
> trying to back out "intelligently" to the pure python implementation
> by itself.
>
> This would make the setup.py implementation much more simple:
> * If --no-cython-compile is here, there's almost nothing to do.
> * If it's not here, add the dependences on the C extensions, extend
> the build_ext distutils command to generate the C files before
> building the cython module, (this is actually easy to do) and...
> voilà! Just exit with an error if you can't generate the C files,
> suggest to try --no-cython-compile instead.

I'm -1 on this idea, because it complicates auto-installation of
(Continue reading)

Permalink | Reply | 3 comments |
headers
Lisandro Dalcin | 1 Apr 2009 02:45
Picon
Gravatar

Re: [Cython] code documentation tool

On Tue, Mar 31, 2009 at 6:51 PM, Martin Gysel <m.gysel@...> wrote:
>
> AFAIK sphinx gets the info for autodoc from the docstring but how does
> this work for you because my docstrings are removed in the module
> (according the cython doc, that's the normal behavior).
>

What are you talking about, Martin? Cython does not removes any
docstring (with a few exceptions for some special methods). However,
perhaps you need to asks Cython to auto-generate signatures for you,
just add the commented line at the very beginning of your modules:

#cython: embedsignature=True

--

-- 
Lisandro Dalcín
---------------
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594
Permalink | Reply | 1 comment |
headers
Stefan Behnel | 1 Apr 2009 08:54
Picon
Favicon

Re: [Cython] Refcount question: SetAttrString


Dag Sverre Seljebotn wrote:
> While ripping out the old temp system (yay!) ...

Thanks for doing that, BTW. This was sooo long overdue.

Stefan
Permalink | Reply | 1 comment |
headers
Dag Sverre Seljebotn | 1 Apr 2009 22:15
Picon
Picon

Re: [Cython] Naive build system

Robert Bradshaw wrote:
> On Mar 31, 2009, at 8:20 AM, Nicolas Dumazet wrote:
>
>> 2009/4/1 Nicolas Dumazet <nicdumz@...>:
>>> I looked at ways to avoid the extra setup.py work, it seems
>>> there's no
>>> "easy way" here.
>>> I thought about extending the distutils build command to build the c
>>> files before the module build, but it's definitely not simple: if the
>>> C files are correctly generated, one would need to register the C
>>> extensions on the fly, once the build process has already started;
>>> and
>>> I'm not sure that this is possible.
>>> And yes, if it is not possible, one would need to write a complex
>>> build system handling the whole compilation chain.
>>
>> Or... the setup.py behavior could be modified:
>> When --no-cython-compile is not provided, if the system is not able to
>> generate the .c, it bails out, spitting out an error, instead of
>> trying to back out "intelligently" to the pure python implementation
>> by itself.
>>
>> This would make the setup.py implementation much more simple:
>> * If --no-cython-compile is here, there's almost nothing to do.
>> * If it's not here, add the dependences on the C extensions, extend
>> the build_ext distutils command to generate the C files before
>> building the cython module, (this is actually easy to do) and...
>> voilà! Just exit with an error if you can't generate the C files,
>> suggest to try --no-cython-compile instead.
>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Martin Gysel | 1 Apr 2009 23:24
Picon
Gravatar

Re: [Cython] code documentation tool

Lisandro Dalcin schrieb:
> On Tue, Mar 31, 2009 at 6:51 PM, Martin Gysel <m.gysel@...> wrote:
>   
>> AFAIK sphinx gets the info for autodoc from the docstring but how does
>> this work for you because my docstrings are removed in the module
>> (according the cython doc, that's the normal behavior).
>>     
>
> What are you talking about, Martin? Cython does not removes any
> docstring (with a few exceptions for some special methods). However,
> perhaps you need to asks Cython to auto-generate signatures for you,
> just add the commented line at the very beginning of your modules:
>
> #cython: embedsignature=True
>   
thx for the hint, now everything works as expected

/martin
Permalink | Reply | 0 comments |
headers
Robert Bradshaw | 2 Apr 2009 00:23
Favicon

Re: [Cython] Refcount question: SetAttrString

On Mar 31, 2009, at 11:54 PM, Stefan Behnel wrote:

> Dag Sverre Seljebotn wrote:
>> While ripping out the old temp system (yay!) ...
>
> Thanks for doing that, BTW. This was sooo long overdue.

I noticed these changes in the -unstable branch too. Yay!

- Robert
Permalink | Reply | 0 comments |
headers
Robert Bradshaw | 2 Apr 2009 00:25
Favicon

Re: [Cython] Naive build system

On Apr 1, 2009, at 1:15 PM, Dag Sverre Seljebotn wrote:

> Robert Bradshaw wrote:
>> On Mar 31, 2009, at 8:20 AM, Nicolas Dumazet wrote:
>>
>>> 2009/4/1 Nicolas Dumazet <nicdumz@...>:
>>>> I looked at ways to avoid the extra setup.py work, it seems
>>>> there's no
>>>> "easy way" here.
>>>> I thought about extending the distutils build command to build  
>>>> the c
>>>> files before the module build, but it's definitely not simple:  
>>>> if the
>>>> C files are correctly generated, one would need to register the C
>>>> extensions on the fly, once the build process has already started;
>>>> and
>>>> I'm not sure that this is possible.
>>>> And yes, if it is not possible, one would need to write a complex
>>>> build system handling the whole compilation chain.
>>>
>>> Or... the setup.py behavior could be modified:
>>> When --no-cython-compile is not provided, if the system is not  
>>> able to
>>> generate the .c, it bails out, spitting out an error, instead of
>>> trying to back out "intelligently" to the pure python implementation
>>> by itself.
>>>
>>> This would make the setup.py implementation much more simple:
>>> * If --no-cython-compile is here, there's almost nothing to do.
>>> * If it's not here, add the dependences on the C extensions, extend
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Cournapeau | 2 Apr 2009 05:02
Picon
Gravatar

Re: [Cython] Naive build system

On Thu, Apr 2, 2009 at 5:15 AM, Dag Sverre Seljebotn

> About SCons, iI meant that as an apropos and strictly about support for
> end users applications. I.e. it's a matter of finding and bundling an
> SCons plugin for Cython in the Tools directory, like we ship an emacs
> mode.

I would not mind giving away my cython tool to cython - the tool in
numscons are almost all independent of numscons, and can be used
directly from scons,

cheers,

David
Permalink | Reply | 0 comments |
headers
Kurt Smith | 2 Apr 2009 22:55
Picon

[Cython] What happened to cython-devel repo?

Hi,

I tried updating my cython-devel, but no luck:

[506]$ pwd
/home/ksmith/Devel/cython/cython-devel

[507]$ hg pull
pulling from http://hg.cython.org/cython-devel
abort: 'http://hg.cython.org/cython-devel' does not appear to be an hg
repository!

Pulling from cython-unstable works, though, and it seems to be the most current.

Kurt
Permalink | Reply | 3 comments |

Gmane