Mailman 3 September 2016 - cython-devel

Re: [Cython] [cython-users] Re: Cython 0.25 alpha0
by Matthew Brett Sept. 26, 2016

Sept. 26, 2016

Hi, On Mon, Sep 26, 2016 at 1:42 AM, Alexey Buluy <kamikazze.ru(a)gmail.com> wrote: > > Who is this smart guy who decided to release this version into the open > without proper testing? > Now all packages in pip which use Cython are failing to install: > >> sudo pip install cassandra-driver==2.7.2 >> Downloading/unpacking cassandra-driver==2.7.2 >> Running setup.py egg_info for package cassandra-driver >> Unable to find pgen, not compiling formal grammar. >> Compiling >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Plex/Scanners.py because it >> changed. >> Compiling >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Plex/Actions.py because it >> changed. >> Compiling >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Lexicon.py because it >> changed. >> Compiling >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Scanning.py because >> it changed. >> Compiling >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Parsing.py because it >> changed. >> Compiling >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Visitor.py because it >> changed. >> Compiling >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/FlowControl.py >> because it changed. >> Compiling >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Code.py because it >> changed. >> Compiling >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Tempita/_tempita.py because it >> changed. >> [1/9] Cythonizing >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Code.py >> [2/9] Cythonizing >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/FlowControl.py >> [3/9] Cythonizing >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Lexicon.py >> [4/9] Cythonizing >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Parsing.py >> [5/9] Cythonizing >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Scanning.py >> [6/9] Cythonizing >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Compiler/Visitor.py >> [7/9] Cythonizing >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Plex/Actions.py >> [8/9] Cythonizing >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Plex/Scanners.py >> [9/9] Cythonizing >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Tempita/_tempita.py >> warning: no files found matching '*.pyx' under directory >> 'Cython/Debugger/Tests' >> warning: no files found matching '*.pxd' under directory >> 'Cython/Debugger/Tests' >> warning: no files found matching '*.h' under directory >> 'Cython/Debugger/Tests' >> warning: no files found matching '*.pxd' under directory >> 'Cython/Utility' >> gcc: error: >> /tmp/easy_install-AEclgi/Cython-0.25a0/Cython/Runtime/refnanny.c: No such >> file or directory >> gcc: fatal error: no input files >> compilation terminated. > > > Anybody knows how to fix this? That's odd - have you set up pip to fetch ``--pre`` packages by default somehow? When I do a pip install on my machine, I get the stable release. The pre-releases, like this one, are precisely to shake out problems before the stable releases. What do you get for a plain: pip install cython Best, Matthew

1 0

Cython 0.25 alpha0
by Robert Bradshaw Sept. 26, 2016

Sept. 26, 2016

Please download and test the upcoming release of Cython: https://github.com/cython/cython/archive/0.25a0.tar.gz This is not the final release (more pull requests and bug fixes may still go in) but a lot has changed since the last release so it'd be good to get feedback early. https://github.com/cython/cython/blob/master/CHANGES.rst Thanks, Robert

4 5

Cython release
by Robert Bradshaw Sept. 18, 2016

Sept. 18, 2016

I'd like to put out another Cython release shortly. Is anyone aware of anything that we should try to get in before then? - Robert

4 8

cygdb: no debug files were found
by Nathan Goldbaum Sept. 14, 2016

Sept. 14, 2016

Hi all, I'm following the directions in the link below to debug some cython code using cygdb: http://docs.cython.org/src/userguide/debugging.html Unfortunately, when I try to actually debug my program using cygdb, I get a "no debug files were found" error. It looks like the error is getting raised here: https://github.com/cython/cython/blob/master/Cython/Debugger/Cygdb.py#L33 So for some reason the "cython_debug" folder isn't being generated at build time. I tried to follow the directions closely, you can see the notes I put together during the installation process here: https://bpaste.net/show/6b11f815d449 Unfortunately the library I'm trying to debug (yt: bitbucket.org/yt_analysis/yt) uses a somewhat nonstandard build setup based on numpy distutils, and I suspect that is breaking some of the assumptions that went into the cygdb instructions in the cython docs. Does anyone have any idea what went wrong here? For now I'm going to fall back to regular gdb, and debug the autogenerated cython sources. Thanks for your help, Nathan Goldbaum

2 1

Minor issue with running tests and -Wlong-long
by Erik Bray Sept. 5, 2016

Sept. 5, 2016

Hello, As some of you already know I've been doing some work on Cython on Cygwin [in the process I I'm constantly mixing the two up in speech, but maybe in writing I'll do better :)]. There are several issues with the tests on Cygwin, and that's one thing I'll work on. But a major annoyance I've encountered when running any tests is a huge number of warnings from gcc such as: embray@PC-pret-47 ~/src/cython $ CFLAGS="-O0" ./runtests.py -vv --no-cpp addloop Python 2.7.10 (default, Jun 1 2015, 18:05:38) [GCC 4.9.2] Running tests against Cython 0.24 f68b5bd0fa620d0dc26166bffe5fe42d94068720 Backends: c runTest (__main__.CythonRunTestCase) compiling (c) and running addloop ... === C/C++ compiler error output: === In file included from /usr/include/python2.7/Python.h:58:0, from addloop.c:4: /usr/include/python2.7/pyport.h:69:27: warning: ISO C90 does not support ‘long long’ [-Wlong-long] #define PY_LONG_LONG long long ^ /usr/include/python2.7/pyport.h:793:34: note: in definition of macro ‘PyAPI_FUNC’ # define PyAPI_FUNC(RTYPE) RTYPE ^ /usr/include/python2.7/intobject.h:46:21: note: in expansion of macro ‘PY_LONG_LONG’ PyAPI_FUNC(unsigned PY_LONG_LONG) PyInt_AsUnsignedLongLongMask(PyObject *); ^ In file included from /usr/include/python2.7/Python.h:58:0, from addloop.c:4: ... And so on. For now an easy workaround is to add -Wno-long-long to the compiler flags. But I was curious why I was seeing this in Cygwin but not on my Ubuntu system, and here's why: In runtests.py there is a check https://github.com/cython/cython/blob/master/runtests.py#L829 if self.language=='c' and compiler='gcc': ext_compile_flags.extend(['-std=c89', '-pedantic']) where in this case `compiler` is assigned `sysconfig.get_config_var('CC')`. On my Linux system this expands to "x86_64-linux-gnu-gcc -pthread". Whereas on Cygwin (and probably many other systems) it expands simply to "gcc". I'm guessing that to do what it intended the above line should read "and 'gcc' in compiler". But this also raises the question: Why are the tests run with these flags? If Python was configured with HAVE_LONG_LONG, then these warnings will be inevitable. Thanks, Erik

2 2