search

libdynd / dynd-python

Python exposure of dynd
http://libdynd.org
Other
119 stars 23 forks source link

Use conda build exclusively to test installation. #734

Closed insertinterestingnamehere closed 8 years ago

insertinterestingnamehere commented 8 years ago

Installing a package from a file url is broken in conda 4.1.8, but it's not something we actually need for our tests anyway.

Should work around https://github.com/conda/conda/issues/2845#issuecomment-233145892.

insertinterestingnamehere commented 8 years ago

This should be good to go. Remaining CI failures appear to be related to https://github.com/libdynd/dynd-python/pull/733#discussion_r71071456.

insertinterestingnamehere commented 8 years ago

How about we go ahead and merge this one so we can at least have some of these issues resolved. @mwiebe any thoughts on the best way to fix the nd/ndt separation here?

mwiebe commented 8 years ago

Sure, merging! I've been working some on getting the datashape parser to be pluggable, which should help for some of the nd/ndt split issues. In talking through some of the details of things with @izaid, it really feels like some subset of the kernel/callable mechanism belongs in the same place as the core data type definitions. For example, defining and implementing destructors is something that is a necessary part of adding a data type, but without being able to define that as a callable, there would end up being another weaker version of the callable mechanism in there.