[Cython] Strange cimport behaviour

[Lars Buitinck]

2011/7/21 Robert Bradshaw <robertwb at math.washington.edu>:
> On Wed, Jul 20, 2011 at 10:30 PM, Robert Bradshaw
> <robertwb at math.washington.edu> wrote:
>> On Wed, Jul 20, 2011 at 9:40 PM, Vitja Makarov <vitja.makarov at gmail.com> wrote:
>>> 2011/7/21 Robert Bradshaw <robertwb at math.washington.edu>:
>>>> I'm not sure what we can do here--we make sure to emit the #include
>>>> statements in the same order as they are encountered in the Cython
>>>> sources because C is sensitive to this kind of thing, but we can't
>>>> really "fix" C. I suppose we could cimport posix.fcntl from within
>>>> posix.unistd to force an ordering.
>
> https://github.com/cython/cython/commit/55d5e576935d83c6bdadc593e36793aecffe0bae

I'm not familiar enough with the Cython internals to understand this
change; are #includes now generated in the C code in the order of the
corresponding cimports?

-- 
Lars Buitinck
Scientific programmer, ILPS
University of Amsterdam