Re: [matplotlib-devel] [Numpy-discussion] Announcing toydist, improving distribution and packaging situation

[Dag Sverre Seljebotn]

Nathaniel Smith  wrote:
> On Sun, Jan 3, 2010 at 4:23 AM, David Cournapeau 
> wrote:
>> Another way is to provide our own repository for a few major
>> distributions, with automatically built packages. This is how most
>> open source providers work. Miguel de Icaza explains this well:
>>
>> http://tirania.org/blog/archive/2007/Jan-26.html
>>
>> I hope we will be able to reuse much of the opensuse build service
>> infrastructure.
>
> Sure, I'm aware of the opensuse build service, have built third-party
> packages for my projects, etc. It's a good attempt, but also has a lot
> of problems, and when talking about scientific software it's totally
> useless to me :-). First, I don't have root on our compute cluster.

I use Sage for this very reason, and others use EPD or FEMHub or
Python(x,y) for the same reasons.

Rolling this into the Python package distribution scheme seems backwards
though, since a lot of binary packages that have nothing to do with Python
are used as well -- the Python stuff is simply thin wrappers around what
should ideally be located in /usr/lib or similar (but are nowadays
compiled into the Python extension .so because of distribution problems).

To solve the exact problem you (and me) have I think the best solution is
to integrate the tools mentioned above with what David is planning (SciPI
etc.). Or if that isn't good enough, find generic "userland package
manager" that has nothing to do with Python (I'm sure a dozen
half-finished ones must have been written but didn't look), finish it, and
connect it to SciPI.

What David does (I think) is seperate the concerns. This makes the task
feasible, and also has the advantage of convenience for the people that
*do* want to use Ubuntu, Red Hat or whatever to roll out scientific
software on hundreds of clients.

Dag Sverre


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] [Numpy-discussion] Announcing toydist, improving distribution and packaging situation

[David Cournapeau]

On Mon, Jan 4, 2010 at 5:48 PM, Dag Sverre Seljebotn
 wrote:

>
> Rolling this into the Python package distribution scheme seems backwards
> though, since a lot of binary packages that have nothing to do with Python
> are used as well

Yep, exactly.

>
> To solve the exact problem you (and me) have I think the best solution is
> to integrate the tools mentioned above with what David is planning (SciPI
> etc.). Or if that isn't good enough, find generic "userland package
> manager" that has nothing to do with Python (I'm sure a dozen
> half-finished ones must have been written but didn't look), finish it, and
> connect it to SciPI.

You have 0install, autopackage and klik, to cite the ones I know
about. I wish people had looked at those before rolling toy solutions
to complex problems.

>
> What David does (I think) is seperate the concerns.

Exactly - you've describe this better than I did

David

--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] doc build problem with axes_grid

[Michael Droettboom]

Eric Firing wrote:
> John Hunter wrote:
>   
>> On Sat, Jan 2, 2010 at 12:34 AM, Eric Firing  wrote:
>> 
>>> Jae-Joon Lee wrote:
>>>   
 Maybe we need something like "python make.py clean"?
 
It already does have "clean", but from the looks of it, it is currently 
broken (I just fixed this in SVN).  It used to call out to svn-clean, 
but it was pointed out that only works if you're building from SVN, not 
from a tarball (which is a problem for the Linux distros).  So there is 
explicit code in make.py to delete all of the generated files.
> Do you know why the plot directive (I assume that is the cause of the 
> problem) cannot put all generated output in build?  Or is this a more 
> general Sphinx wart?
>   
The problem is not in the plot_directive (though I suppose it could be 
more helpful when the file isn't found) -- it does in fact put 
everything under build.  The problem is in gen_rst.py, which generates 
pages for all of the examples, and puts them in doc/examples.  At the 
time, it wasn't clear how to generate these pages under the build tree 
and then have Sphinx pick them up.  That may have predated all of the 
"hooks" that Sphinx now has, however, and it may now be possible to 
solve that problem.

Mike

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] building of latex docs failing at barb_demo.pdf

[Michael Droettboom]

Hmm...  I can't reproduce this locally.  But it looks like it's using 
doctree files cached from a previous run.

I'll try calling "python make.py clean" before "python make.py all" in 
the _buildbot_doc.sh (at least temporarily), to try to get a complete 
build log which might offer more clues.

Mike

Andrew Straw wrote:
> Hi,
>
> With the recent regression fixed in Pygments, the doc auto-builder is
> closer to completing successfully. However, there's a new bug. The build
> ends with:
>
> LaTeX Warning: File 
> `/home/mpl-chslave/slave-py25/build_docs/build/doc/build/pl
> ot_directive/mpl_examples/pylab_examples/barb_demo.pdf' not found on input 
> line
>  28650.
>
>
> !pdfTeX error: pdflatex (file 
> /home/mpl-chslave/slave-py25/build_docs/build/doc
> /build/plot_directive/mpl_examples/pylab_examples/barb_demo.pdf): cannot find 
> i
> mage file
>  ==> Fatal error occurred, no output PDF file produced!
>
>
> Anyone have a clue what is going on here?
>
> Feel free to check in the attempted solution and the buildbot will
> automatically try it. (See the "
> Ubuntu
> 8.04, Python 2.5, amd64 (docs)" column at
> http://mpl-buildbot.code.astraw.com/waterfall )
>
> Waiting for this will take up to 20 minutes before the build is
> triggered (10 minute polling on the svn repo, and a 10 minute timeout
> before any build is started in case another commit comes in). So you can
> also force a build by clicking the column title ("Ubuntu 8.04, Python
> 2.5, amd64 (docs)" and then clicking the "Force Build" button.
>
> It will be great to get the buildbot automatically building the svn docs
> successfully.
>
> -Andrew
>
> --
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] building of latex docs failing at barb_demo.pdf

[Michael Droettboom]

Cleaning the docs first seems to have fixed it.

Is there a way to download the build products (i.e. the PDF file produced)?

Mike

Michael Droettboom wrote:
> Hmm...  I can't reproduce this locally.  But it looks like it's using 
> doctree files cached from a previous run.
>
> I'll try calling "python make.py clean" before "python make.py all" in 
> the _buildbot_doc.sh (at least temporarily), to try to get a complete 
> build log which might offer more clues.
>
> Mike
>
> Andrew Straw wrote:
>   
>> Hi,
>>
>> With the recent regression fixed in Pygments, the doc auto-builder is
>> closer to completing successfully. However, there's a new bug. The build
>> ends with:
>>
>> LaTeX Warning: File 
>> `/home/mpl-chslave/slave-py25/build_docs/build/doc/build/pl
>> ot_directive/mpl_examples/pylab_examples/barb_demo.pdf' not found on input 
>> line
>>  28650.
>>
>>
>> !pdfTeX error: pdflatex (file 
>> /home/mpl-chslave/slave-py25/build_docs/build/doc
>> /build/plot_directive/mpl_examples/pylab_examples/barb_demo.pdf): cannot 
>> find i
>> mage file
>>  ==> Fatal error occurred, no output PDF file produced!
>>
>>
>> Anyone have a clue what is going on here?
>>
>> Feel free to check in the attempted solution and the buildbot will
>> automatically try it. (See the "
>> Ubuntu
>> 8.04, Python 2.5, amd64 (docs)" column at
>> http://mpl-buildbot.code.astraw.com/waterfall )
>>
>> Waiting for this will take up to 20 minutes before the build is
>> triggered (10 minute polling on the svn repo, and a 10 minute timeout
>> before any build is started in case another commit comes in). So you can
>> also force a build by clicking the column title ("Ubuntu 8.04, Python
>> 2.5, amd64 (docs)" and then clicking the "Force Build" button.
>>
>> It will be great to get the buildbot automatically building the svn docs
>> successfully.
>>
>> -Andrew
>>
>> --
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev 
>> ___
>> Matplotlib-devel mailing list
>> Matplotlib-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>   
>> 
>
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] building of latex docs failing at barb_demo.pdf

[Andrew Straw]

Michael Droettboom wrote:
> Cleaning the docs first seems to have fixed it.
>
> Is there a way to download the build products (i.e. the PDF file 
> produced)?
That, and testing for doc build failures, is the point, although I 
managed to screw up the uploading until now. However, I believe I have 
fixed this and we should now have auto-built docs from svn trunk at:

http://matplotlib.sourceforge.net/trunk-docs
http://matplotlib.sourceforge.net/trunk-docs/Matplotlib.pdf

Perhaps we should link these from somewhere. And the URLs can certainly 
be changed without much difficulty.

Thanks for finding the clean step issue -- I thought the buildbot 
software automatically cleaned the working directory on every build, but 
obviously I thought wrong.

-Andrew

--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel