Just a quick note: I've looked at the repo, and I'll go over the code soon.
I don't want to add the whole thing to 0.5 -- that will be out soon and
has already enough new features. Instead, we can let autosummary mature,
and include it in 0.6 (which won't be as long as 0.5 was from 0.4, I
Sphinx autodoc has 'signals' that the user can hook into, to mangle the
docstrings and function signatures before autodoc processes them. This is
useful if the docstring format is not native Sphinx format, or if
Sphinx's function signature introspection fails and the user has some
Thanks for finding that bug Paul!
And yes, there is a ton of functionality in the Numpy stuff. I wanted
a good base to build from, and a clean slate to pull in intelligible
numpy stuff.
- Hooking autosummary into the same autodoc-process-docstring
and autodoc-process-signature signal as
Pull request sent. I love bit-bucket :).
cheers.
-chris
On Nov 4, 3:07 pm, percious [EMAIL PROTECTED] wrote:
Thanks for finding that bug Paul!
And yes, there is a ton of functionality in the Numpy stuff. I wanted
a good base to build from, and a clean slate to pull in intelligible
numpy
To whom it may concern, I have started my own autosummary branch at:
http://bitbucket.org/percious/sphinx-autosummary/
I will keep you abreast when I think I have something worthy of
merging with trunk.
cheers!
-chris
On Nov 2, 3:38 am, Nicola Larosa (tekNico) [EMAIL PROTECTED]
wrote:
Georg
Georg Brandl wrote:
So, I'm asking all of you: what would you prefer -- SVN at Google,
with very liberal commit policies, or Mercurial?
I'll cast my vote too, FWIW.
+1 for Mercurial.
+0 for Bazaar-NG.
-1 for git. Let's be pythonic in tools too, as far as possible.
--
Nicola Larosa -
On Sat, Nov 01, 2008 at 04:14:10PM +0100, Georg Brandl wrote:
So, I'm asking all of you: what would you prefer -- SVN at Google,
with very liberal commit policies, or Mercurial?
My experience is that DVCS makes a big difference. I really enjoy it.
Gaël
On Sat, Nov 1, 2008 at 4:14 PM, Georg Brandl [EMAIL PROTECTED] wrote:
So, I'm asking all of you: what would you prefer -- SVN at Google,
with very liberal commit policies, or Mercurial?
i'm not (yet) a contributor, but i'm working extensivly with sphinx
last month and will continue in the
DVCS is nice - and lightweight on a potential contributor's local machine..
Could we keep it python-ish, so that contributing platforms don't get in the
way?
The nice thing about SVN is is seems to run everywhere
mercurial too (but you need to compile C code if not);
bazaar is all python;
I'm using everything Launchpad, including Bazaar, for my project. That said,
I'm still learning DVCS and Bazaar, but I like all the support tools that
Launchpad provides, and that they're all in one place, and that there's
money behind development.
On Sat, Nov 1, 2008 at 12:15 PM, Yarko T [EMAIL
On Sat, Nov 1, 2008 at 19:15, Yarko T [EMAIL PROTECTED] wrote:
I'd vote for one of the later two (hg or bzr). In fact, I've found a most
of what I need bazaar site (launchpad), but not found a hosting place
similarly configured for hg, so would be curious to hear what other people
are using
alternate possibility to directly take the step to a DVCS.
So, I'm asking all of you: what would you prefer -- SVN at Google,
with very liberal commit policies, or Mercurial?
While I am not contributing to sphinx, I'd like to support the vote
for Mercurial. I have used over the years cvs
I used to be on the hg end also - but I was participating in projects on
Launchpad; that started to erode my preference I think later (1.5?)
releases of bzr are snappier...
Anyway - the supporting environment is important (look at sourceforge,
code.google, launchpad...)
Sebastian: thanks
I think Project Kenai bears more looking into (at least by me...)... At
first look, it seems pretty feature reach.
On Sat, Nov 1, 2008 at 2:46 PM, Sebastien Douche [EMAIL PROTECTED] wrote:
On Sat, Nov 1, 2008 at 19:15, Yarko T [EMAIL PROTECTED] wrote:
I'd vote for one of the later two (hg
14 matches
Mail list logo
