I think you gave me the answers:
0) It seems reasonable to just use sphinx,
no jekyll or anything more, only if a need for it is found.
I might use some HTML generated by vimwiki for pure convenience.
1) Make the main documentation with sphinx.
That means joining:
and
2) github.io, gitbook,
On Thu, Feb 1, 2018 at 7:38 AM, Renato Fabbri
wrote:
>
> Dear Scipy-ers,
>
> If you think I should split the message so that
> things get more clear...
>
> But the things are:
> 1) How to document numpy-heavy projects?
There is nothing particularly special about
On 31.01.2018 17:58, Chris Barker wrote:
> I'm guessing you could use Cython to make this easier.
... or Boost.Python (http://boostorg.github.io/python), which has
built-in support for NumPy
(http://boostorg.github.io/python/doc/html/numpy/index.html), and
supports both directions: extending
I'm guessing you could use Cython to make this easier. It's usually used
for calling C from Python, but can do the sandwich in both directions...
Just a thought -- it will help with some of that boilerplate code...
-CHB
On Tue, Jan 30, 2018 at 10:57 PM, Jialin Liu wrote:
>
Dear Scipy-ers,
If you think I should split the message so that
things get more clear...
But the things are:
1) How to document numpy-heavy projects?
2) How to better make these contributions available
to the numpy/scipy community?
Directions will be greatly appreciated.
I suspect that this
On 01/31/2018 02:06 AM, Joe wrote:
Does someone know of a function or a convenient way to automatically
derive a dtype object from a C typedef struct string or a cffi.typeof()?
I remember when I wrote those docs over a year ago, I searched for an
established way to do this but didn't find