On 28 January 2013 15:57, Michael Droettboom <md...@stsci.edu> wrote:
> Thanks. Sorry about not communicating the new dependency very well. As
> this only affects those building the docs (meaning primarily developers and
> not end-users) it wasn't given the same care.
>
That's fine. I think I did see the discussion, but I didn't pay it much
attention.
> We had had some back-and-forth about whether to include a local copy of
> numpydoc in matplotlib, but ultimately decided not to as this is generally
> not what packagers like to see. In there a way to depend on numpydoc from
> the development release in your PPA (only as a build-time dependency?)
>
If we want builds for pre-raring versions, I think the way to do it would
be to backport the numpydoc package, and put it in the PPA - it will use
packages in the same PPA to satisfy build dependencies. This is easy enough
to do if people want it, I'm just aware that each build runs for the best
part of an hour*, on two architectures times however many releases we
target. If people are actually interested in running the daily packages,
that's worth doing, but if not, I don't want to tie up Launchpad's build
farm. My own use was the Python 3 package, which 1.2.0 can now meet.
*If that seems like a long build time, it has to set up build dependencies,
build and test four times (Python 2 & 3, normal & debug), and build the
docs. It's about an hour on i386 (which does the docs), and about half an
hour on amd64.
Thomas
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
