Mailman 3 February 2011 - cython-devel

Re: [Cython] [cython-users] Cython .pxd introspection: listing defined constants
by W. Trevor King Feb. 17, 2011

Feb. 17, 2011

On Thu, Feb 17, 2011 at 10:53:15AM -0300, Lisandro Dalcin wrote: > Cython could certainly support "cpdef struct", it is just a matter to > define a proposal and find a contributor to implement it :-) Is there a CEP template (a la PEPs 9 and 12) that should be discussed on the mailing list, or do I develop it free-form on the wiki [2]? p.s. should I be picking one of cython-dev@codespeak or cython-devel@python? Is the shift not yet official? [2]: http://wiki.cython.org/enhancements/ -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt

2 1

[PATCH] Add .gitignores to cython and cython-docs
by W. Trevor King Feb. 17, 2011

Feb. 17, 2011

Here's a pair of patches doing just that. I also ignore *.c in cython, because all .c files are currently auto-generated. Perhaps that will not always be the case? If it seems to risky, feel free to leave that part out. -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt

1 0

Outdated `hg export` on cython-devel homepage
by W. Trevor King Feb. 17, 2011

Feb. 17, 2011

The `hg export` on the cython-devel page [1] should probably be changed to (or additionally list) `git format-patch`, now that Cython's versioned in Git. Keeping the `hg export` reference might be useful for Mercurial lovers using hg-git. [1]: http://mail.python.org/mailman/listinfo/cython-devel -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt

2 1

documentation tarball
by Jason Grout Feb. 17, 2011

Feb. 17, 2011

Would it be too much trouble to post a snapshot of the cython-docs tree along with a cython release? I see the git repository for cython-docs, but it would be more convenient for an end-user who wants a copy of the docs to not have to search through the commit log to find the right commit corresponding to a release. For example, it would be great if a zip or tarball of the documentation for 0.14.1 was posted on the cython.org homepage in the Download section, perhaps with text like this: The latest release of Cython is 0.14.1 (released 2011-02-04). You can download it as a gzipped tar or as a zip file. The documentation is also available (gzipped tar or zip). Thanks, Jason

1 0

Re: [Cython] Possible Freeze-related regression from 0.14 to 0.14.1
by Matthew Fox Feb. 16, 2011

Feb. 16, 2011

Of course I would forget to attach the test case. Let's try again. > -----Original Message----- > From: Matthew Fox > Sent: February-16-11 11:22 AM > To: 'cython-devel(a)python.org' > Subject: Possible Freeze-related regression from 0.14 to 0.14.1 > > My project using Cython-freeze compiles properly with Cython 0.14.0 but > fails with 0.14.1. I run Python 2.5 on Debian Lenny and the > cython_freeze from github (October 29, 2009). The attached simple test > case (1 plain .pyx and .pxd, 1 .pyx with main(), and a makefile) > demonstrates the issue- it works under 0.14.0 and fails under 0.14.1. > > The issue appears to be that Cython 0.14.0 declares an "int > __pyx_module_is_main_mainster = 0" in mainster.c, while 0.14.1 declares > it as static: "static int __pyx_module_is_main_ mainster = 0". When > linking the object files, this results in the error from GCC: > > gcc -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions - > L/usr/lib/python2.5/config executable.o mainster.o foo.o -lpython2.5 > -lm -lpthread -ldl -lutil -o executable > executable.o: In function `main': > [...]/executable.c:54: undefined reference to > `__pyx_module_is_main_mainster' > collect2: ld returned 1 exit status > make: *** [executable] Error 1 > > If I remove "static" from the declaration in mainster.c, I can > recompile it and link the object files as I could do with Cython > 0.14.0. > > Let me know if you need more details or if it's not a bug at all and > there's a workaround. My workaround for now will be to use 0.14.0. > > Thanks, > Matt Fox > > > > Phone: 604-824-2770 x305 > Toll free: 800-360-2319 > Email: matthew(a)kerkhofftech.ca > Web: http://www.kerkhofftech.ca

1 0

Possible Freeze-related regression from 0.14 to 0.14.1
by Matthew Fox Feb. 16, 2011

Feb. 16, 2011

My project using Cython-freeze compiles properly with Cython 0.14.0 but fails with 0.14.1. I run Python 2.5 on Debian Lenny and the cython_freeze from github (October 29, 2009). The attached simple test case (1 plain .pyx and .pxd, 1 .pyx with main(), and a makefile) demonstrates the issue- it works under 0.14.0 and fails under 0.14.1. The issue appears to be that Cython 0.14.0 declares an "int __pyx_module_is_main_mainster = 0" in mainster.c, while 0.14.1 declares it as static: "static int __pyx_module_is_main_ mainster = 0". When linking the object files, this results in the error from GCC: gcc -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions -L/usr/lib/python2.5/config executable.o mainster.o foo.o -lpython2.5 -lm -lpthread -ldl -lutil -o executable executable.o: In function `main': [...]/executable.c:54: undefined reference to `__pyx_module_is_main_mainster' collect2: ld returned 1 exit status make: *** [executable] Error 1 If I remove "static" from the declaration in mainster.c, I can recompile it and link the object files as I could do with Cython 0.14.0. Let me know if you need more details or if it's not a bug at all and there's a workaround. My workaround for now will be to use 0.14.0. Thanks, Matt Fox Phone: 604-824-2770 x305 Toll free: 800-360-2319 Email: matthew(a)kerkhofftech.ca Web: http://www.kerkhofftech.ca

1 0

Fwd: Re: Cython builds on various Debian platforms
by Stefan Behnel Feb. 16, 2011

Feb. 16, 2011

[forwarding to the list, from Yaroslav Halchenko] Hi, I am a member of Python Applications Packaging Team in Debian. So now me, later some other members could chime in to provide fresh uploads. On Tue, 15 Feb 2011, Stefan Behnel wrote: > Cool. That looks good. As you mentioned, it doesn't include the test > runs yet, but it would be really great if you could get those > running. great to hear to be on the same page ;) the only additional concern I see is the duration -- it might torture build boxes for old/exotic architectures quite a bit... there are no timeouts (like with ctest platform -- got bitten by them a few times already) among your tests, aren't there? (just want to make sure) > I am a bit surprised that each platform compiles the Cython modules > several times according to the logs. Is that intended? should build once per each supported python version (currently 2.5 and 2.6) and for debug builds of those supported versions... looking into the log, indeed building seems to be invoked twice though -- I guess my fault with build/cython.1: build where build is a PHONY. I will look into it for the next upload: $> wget -O- -q https://buildd.debian.org/fetch.cgi\?pkg\=cython\;ver\=0.14.1-1\;arch\=hurd… | grep -B2 -A2 setup.py for buildver in 2.5 2.6; do \ cd /build/buildd-cython_0.14.1-1-hurd-i386-fJZAFo/cython-0.14.1 && cd . && \ python$buildver setup.py clean \ -a; \ done -- set -e; for buildver in 2.5 2.6; do \ cd /build/buildd-cython_0.14.1-1-hurd-i386-fJZAFo/cython-0.14.1 && cd . && \ python$buildver setup.py build \ --build-base="/build/buildd-cython_0.14.1-1-hurd-i386-fJZAFo/cython-0.14.1/./build"; \ done -- set -e; for buildver in 2.5 2.6; do \ cd /build/buildd-cython_0.14.1-1-hurd-i386-fJZAFo/cython-0.14.1 && cd . && \ python$buildver setup.py build \ --build-base="/build/buildd-cython_0.14.1-1-hurd-i386-fJZAFo/cython-0.14.1/./build"; \ done -- set -e; for buildver in 2.5 2.6; do \ cd /build/buildd-cython_0.14.1-1-hurd-i386-fJZAFo/cython-0.14.1 && cd . && \ python$buildver setup.py install \ --root="/build/buildd-cython_0.14.1-1-hurd-i386-fJZAFo/cython-0.14.1/debian/cython" \ --install-purelib=/usr/lib/python$buildver/site-packages/ \ -- dh_installdirs -pcython-dbg for i in 2.5 2.6; do \ python$i-dbg ./setup.py install --prefix=/usr --no-compile -O0 \ --root /build/buildd-cython_0.14.1-1-hurd-i386-fJZAFo/cython-0.14.1/debian/cython-dbg; \ done -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic

1 0

Cython builds on various Debian platforms
by Stefan Behnel Feb. 15, 2011

Feb. 15, 2011

[CC-ing cython-devel here] Yaroslav Halchenko is Cython's current maintainer for Debian. Yaroslav Halchenko, 15.02.2011 19:50: >> Stefan Behnel, 15.02.2011 18:54: >>> Yaroslav Halchenko, 14.02.2011 21:38: >>>> I guess it might bring us >>>> surprises while building on those exotics platforms Debian supports ;) >>> >>> I don't really hope for major surprises, but it sure would be great to >>> support those platforms. >> >> BTW, I assume the build results are publicly available somewhere? > > SURE! > > as for packages: > ftp://ftp.debian.org/debian/pool/main/c/cython/ > > but more interesting -- logs > http://packages.qa.debian.org/c/cython.html > > is the top page for 'Debian developer information' on cython (you > might like to subscribe to the package tracking -- lower left corner). > > for builds across platforms go to the link "buildd: logs": > https://buildd.debian.org/pkg.cgi?pkg=cython > > so 0.14.1-1 was already built ok across platforms seems to me ;) Cool. That looks good. As you mentioned, it doesn't include the test runs yet, but it would be really great if you could get those running. I am a bit surprised that each platform compiles the Cython modules several times according to the logs. Is that intended? Stefan

1 0

Re: [Cython] Control flow graph
by Vitja Makarov Feb. 15, 2011

Feb. 15, 2011

2011/2/15 Vitja Makarov <vitja.makarov(a)gmail.com>: > 2011/2/15 Robert Bradshaw <robertwb(a)math.washington.edu>: >> On Sun, Feb 13, 2011 at 11:40 PM, Vitja Makarov <vitja.makarov(a)gmail.com> wrote: >>> Hi! >>> >>> In order to implement "reaching definitions" algorithm. >>> I'm now working on control-flow (or data-flow) graph. >>> >>> Here is funny picture made with graphviz ;) >>> >>> http://piccy.info/view3/1099337/ca29d7054d09bd0503cefa25f5f49420/1200/ >> >> Cool. Any plans on handling exceptions? >> > Ooops forget to CC cython-devel... Sure, but I don't have much time for this :( Linear block inside try...except body should be split by assignments and each subblock should point to exception handling entry point. As result I want to have set of possible assignments for each NameNode position. So handling of uninitialized variables, unused, unused results should be easy, later it may help to implement local variable deletion. And guess that could help type inference. -- vitja.

1 0

Control flow graph
by Vitja Makarov Feb. 14, 2011

Feb. 14, 2011

Hi! In order to implement "reaching definitions" algorithm. I'm now working on control-flow (or data-flow) graph. Here is funny picture made with graphviz ;) http://piccy.info/view3/1099337/ca29d7054d09bd0503cefa25f5f49420/1200/ -- vitja.

4 3