Hi! Suppose we have a C-library (as part of MeatAxe), which is provided by an *optional* package. I would like to have a Cython wrapper in the SageMath library.
How can that be done? If there is a Cython file in src/sage/ that uses the optional package, then its compilation will fail, unless the optional package is installed. Shall the optional package install code in src/sage/... and launch "sage -b"? In that way, the Cython file would only be present if the condition for its compilation is available. But it somehow seems rather intrusive to let an optional package install Cython files in the src/sage tree. Is it possible to have Cython files in src/sage/... that are only compiled if a certain optional package is installed? That's not the same as a dependency: A dependency would mean that the attempt to compile the Cython file would trigger installation of the optional package---Instead, I want that the Cython file is ignored by "sage -b" unless the optional package was installed by the user. Or should I go for a different approach: Do NOT put the wrapper into src/sage, but keep the wrapper in the optional package. Hence, it is not used as "from sage.matrix.meataxe import ...", but as "from meataxe import ..."? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
