On Thu, Apr 19, 2012 at 12:48 PM, Emil <emi...@gmail.com> wrote: > On 19 April 2012 07:20, Robert Bradshaw <rober...@math.washington.edu> wrote: >> It might be distutils. It might be Cython. It might even be Sage or >> Python. But without knowing exactly how you're trying to >> compile/install your package, it's hard if not impossible to give any >> specific recommendations on what to change to get the result you want. > > Thanks Robert, but I've actually just managed to accidentally fix the problem!
That's good to hear. > I added an ext_package='...' declaration to the setup.py file, which > broke things, but when I removed it and reinstalled, everything > worked! I don't know what to make of all this..... > > I'd really like to see more documentation on how to distribute > packages for Sage that are not intended to part of Sage proper. I > can't volunteer for this myself (at present) as I barely understand > how things work and have only managed to get something working by > accident. There should be little, if any, difference from how you would write a Python package outside of the Sage context. (In fact, I can't think of anything sage-specific to add...) While it's widely acknowledge that the Python packaging ecosystem is far from ideal, looking at more generic resources (e.g. distutils, setuptools, or in the Python documentation itself) should help. - Robert -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
