OK, that worked. I uploaded Windows binaries, which include all test files.
Christoph
On 5/29/2013 5:34 PM, Michael Droettboom wrote:
> Must be a problem with the upload. I'm reuploading it now. I'm not
> going to bother upping the version -- it's just the result of a failed
> transfer apparen
On 05/29/2013 05:19 PM, Russell E. Owen wrote:
In article <51a64bcf.80...@stsci.edu>,
Michael Droettboom
wrote:
I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
Once the binaries from Christoph and Russell have been uploaded, I'll
make a broader announcement to get some testing
On 05/29/2013 05:23 PM, Russell E. Owen wrote:
> In article <51a51603.5030...@stsci.edu>,
> Michael Droettboom
> wrote:
>
>> I am going to hold off one more day on making the release candidate.
>> There are three blocker bugs that were discovered over the weekend and
>> I'd like to give them a
Great news! Thank you Dr. Langtangen for arranging this, and Fernando
and the rest of the NumFOCUS board for making it happen!
Cheers,
Mike
On 05/29/2013 04:02 PM, Fernando Perez wrote:
> Hi all,
>
> I just wanted to let you all know that Hans Petter Langtangen,
> well-known author of books on
Must be a problem with the upload. I'm reuploading it now. I'm not
going to bother upping the version -- it's just the result of a failed
transfer apparently.
Mike
On 05/29/2013 04:12 PM, Christoph Gohlke wrote:
> Sorry, but that tarball does not include setup.py and other files. It is
> only
On May 29, 2013, at 4:01 PM, Chris Barker - NOAA Federal
wrote:
> On Wed, May 29, 2013 at 2:19 PM, Russell E. Owen wrote:
>
>> I guess we could serve the associated packages (pytz, dateutil and six),
>> or if they can be installed by pip, ask users to install those. But
>> users using binary i
On Wed, May 29, 2013 at 2:19 PM, Russell E. Owen wrote:
> I guess we could serve the associated packages (pytz, dateutil and six),
> or if they can be installed by pip, ask users to install those. But
> users using binary installers may not even have pip available, so it's a
> big initial hurdle.
In article <51a51603.5030...@stsci.edu>,
Michael Droettboom
wrote:
> I am going to hold off one more day on making the release candidate.
> There are three blocker bugs that were discovered over the weekend and
> I'd like to give them a chance for review first:...
Thanks for the update.
T
In article <51a64bcf.80...@stsci.edu>,
Michael Droettboom
wrote:
> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>
> Once the binaries from Christoph and Russell have been uploaded, I'll
> make a broader announcement to get some testing of this in advance of
> the final releas
Sorry, but that tarball does not include setup.py and other files. It is
only ~25 MB.
Christoph
On 5/29/2013 12:48 PM, Michael Droettboom wrote:
> Ok, folks. 1.3.0rc2 is here:
>
> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc2/matplotlib-1.3.0rc2.tar.gz
>
>
Hi all,
I just wanted to let you all know that Hans Petter Langtangen,
well-known author of books on scientific Python and long-time champion
of these tools at the University of Oslo for many years, has arranged
for a donation of $10,000 to support matplotlib's development.
Hans Petter is the Dir
Ok, folks. 1.3.0rc2 is here:
https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc2/matplotlib-1.3.0rc2.tar.gz
Mike
On 05/29/2013 03:41 PM, Michael Droettboom wrote:
> On 05/29/2013 03:30 PM, Christoph Gohlke wrote:
>> Removing the hardcoded paths works.
>>
>> I
On 05/29/2013 03:30 PM, Christoph Gohlke wrote:
> Removing the hardcoded paths works.
>
> I noticed two more build issues.
>
> 1) On Python 3.x I see the following errors/warnings, however the
> build succeeds.
>
> ```
> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\artist.py
> line
Removing the hardcoded paths works.
I noticed two more build issues.
1) On Python 3.x I see the following errors/warnings, however the build
succeeds.
```
Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\artist.py
line 1265: ParseError: bad token: type=55, value="'", context=('',
(
It seems that in the setuptools way [TM] it is rather difficult to not
include this folder. Does it work if you only remove those hardcoded
paths? It should be easy for me to fix that by not having it search for
system libraries when building a tarball.
Mike
On 05/29/2013 02:55 PM, Christoph
On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
> Hi,
>
> minor issue: the tarball contains a lib\matplotlib.egg-info directory.
> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and
> therefore fails to build on my system. Deleting the
> lib\matplotlib.egg-info folder works.
Doh. T
Hi,
minor issue: the tarball contains a lib\matplotlib.egg-info directory.
The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and therefore
fails to build on my system. Deleting the lib\matplotlib.egg-info folder
works.
Does the release announcement mention that Windows binaries won't
I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
Once the binaries from Christoph and Russell have been uploaded, I'll
make a broader announcement to get some testing of this in advance of
the final release.
The tarball is available here:
https://downloads.sourceforge.net/project/ma
18 matches
Mail list logo
