No. Python2 is obsolete, old style classes even more so.
On Thu, Jan 25, 2018 at 12:22 PM Jeroen Demeyer wrote:
> Do we want to support Python 2 old-style classes for multiple
> inheritance? Personally, I don't think that we should, but it's
> something that has to be decided.
>
> The reason I
I'm of the opinion that the simplicity of GitHub Issues is a plus in many
ways.
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
It's not clear to me what you're doing, but it all sounds too complicated
to me. I have Cython extensions that depend on C++ code, and I don't have
to resort to these kinds of contortions.
One model that works well is to build your C code as a shared library.
Make each Cython module in a single f
On Thu, Jun 9, 2016 at 2:49 AM, Nathaniel Smith wrote:
> On Wed, Jun 8, 2016 at 10:37 PM, Elizabeth A. Fischer
> wrote:
> > Spack gives you complete control over your compiler. This is important
> if
> > you're building Python extensions, especially C++-based exten
>
> Or maybe by default it can just point the user to an Installation Page
> which explains in detail what needs to be done to get those headers for
> various systems ?
I think having this information on an installation instruction page is
definitely a good idea. I don't think it makes sense to
