> >> Is there an option to use an #include for the standard stuff? > > There are upsides and downsides to that as well.
Hence an option. But it could be work to implement so I’m just exploring at the moment. > The way > things are, the generated file is self-contained, and can > be shipped without worrying about it becoming disconnected > from a compatible version of the include file. This is > important when details of the support code can change > without notice between Cython releases. Yes, and in this case an include file may actually be better because it will upgrade with Cython. YMMV I guess. But the main reason is to remove a lot of useless clutter. — John Skaller skal...@internode.on.net _______________________________________________ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
