Hi,
How about splitting doc/sphinxext out from the main Numpy repository to
a separate `numpydoc` repo under Numpy project?
It's a separate Python package, after all. Moreover, this would make it
easier to use it as a git submodule (e.g. in Scipy). Moreover, its
release cycle is not in any
On Wed, Jul 24, 2013 at 5:33 PM, Pauli Virtanen p...@iki.fi wrote:
How about splitting doc/sphinxext out from the main Numpy repository to
a separate `numpydoc` repo under Numpy project?
That would be great, also for scikits that rely on these extensions.
Stéfan
On Wed, Jul 24, 2013 at 4:33 PM, Pauli Virtanen p...@iki.fi wrote:
Hi,
How about splitting doc/sphinxext out from the main Numpy repository to
a separate `numpydoc` repo under Numpy project?
It's a separate Python package, after all. Moreover, this would make it
easier to use it as a git
On Wed, 24 Jul 2013, Pauli Virtanen wrote:
How about splitting doc/sphinxext out from the main Numpy repository to
a separate `numpydoc` repo under Numpy project?
+1
It's a separate Python package, after all. Moreover, this would make it
easier to use it as a git submodule (e.g. in
On Jul 24, 2013, at 10:33 AM, Pauli Virtanen p...@iki.fi wrote:
Hi,
How about splitting doc/sphinxext out from the main Numpy repository to
a separate `numpydoc` repo under Numpy project?
It's a separate Python package, after all. Moreover, this would make it
easier to use it as a git
On 24.07.2013 17:33, Pauli Virtanen wrote:
Hi,
How about splitting doc/sphinxext out from the main Numpy repository to
a separate `numpydoc` repo under Numpy project?
+1
-- Andreas
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
24.07.2013 18:33, Pauli Virtanen kirjoitti:
How about splitting doc/sphinxext out from the main Numpy repository to
a separate `numpydoc` repo under Numpy project?
Done:
https://github.com/numpy/numpydoc
https://github.com/numpy/numpy/pull/3547
https://github.com/scipy/scipy/pull/2657
