Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 8 August 2013 09:56, Russell E. Owen wrote: > BTW: pip refuses to install pytz for me, claiming a suitable version was > not found, and listing dozens of versions. Anyone else seen this? I > don't recall seeing it before recently. I ended up downloading the > source and using distutils. > Rec

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

In article , "Russell E. Owen" wrote: > In article <51fbb996.5030...@stsci.edu>, > Michael Droettboom > wrote: > > > Ludwig, this is one of the most entertaining e-mails I've read in a > > while, and I think your arguments make a lot of sense. > > > > Given infinite developer resources, d

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

I am glad that the numpy and scipy projects are still creating binary installers for python.org python, but it is a serious problem for users of the matplotlib binary installers that they are so difficult to find. If a user googles for "numpy download" then the user finds this page

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On Wed, Aug 7, 2013 at 4:00 PM, Thomas Kluyver wrote: > On 7 August 2013 12:54, Russell E. Owen wrote: > >> P.S. the Mac binary installer for numpy used to be easy to find. I was >> quite dismayed to find how buried it had become when I went looking for >> it a week or two ago. >> > > Is this do

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 7 August 2013 12:54, Russell E. Owen wrote: > P.S. the Mac binary installer for numpy used to be easy to find. I was > quite dismayed to find how buried it had become when I went looking for > it a week or two ago. > Is this down to the redesign of the SciPy site. If so, blame me ;-). I felt,

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

In article <51fbb996.5030...@stsci.edu>, Michael Droettboom wrote: > Ludwig, this is one of the most entertaining e-mails I've read in a > while, and I think your arguments make a lot of sense. > > Given infinite developer resources, do you think there's any logic to > providing *both* syst

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

Doh! Thanks for pointing that out. Mike On 08/02/2013 10:52 AM, Jason Grout wrote: > On 7/31/13 8:38 AM, Michael Droettboom wrote: >> I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to >> all involved! It was a long slog getting this release out, and I >> appreciate everyone

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 7/31/13 8:38 AM, Michael Droettboom wrote: > I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to > all involved! It was a long slog getting this release out, and I > appreciate everyone's patience. > > Once we have binaries uploaded to SourceForge, I will make a formal > anno

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

Ludwig, this is one of the most entertaining e-mails I've read in a while, and I think your arguments make a lot of sense. Given infinite developer resources, do you think there's any logic to providing *both* system Python and python.org based binaries? How much additional work would that be?

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

Oops, I noticed that my lengthy previous email lost the quotes around Russell's comment at the start. It should begin with: > Is it useful in the long term to have such a packager? My impression is > that as soon as packaging is more robust we'll switch to using pip or > easy_install. Hope t

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

Hi Russell (and Mike), Is it useful in the long term to have such a packager? My impression is that as soon as packaging is more robust we'll switch to using pip or easy_install. First off, sorry for the long email - got a bit carried away :-) The summary is that I propose we keep the dmg instal

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 07/31/2013 07:40 PM, Russell E. Owen wrote: > In article <51f997f0.5060...@stsci.edu>, > Michael Droettboom > wrote: > >> On 07/31/2013 05:05 PM, Russell E. Owen wrote: >>> In article <51f950cb.7060...@stsci.edu>, >>>Michael Droettboom >>>wrote: >>> On 07/31/2013 01:47 PM, Rus

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

I have made this little example image less wide directly on the website, and in the source in a1921d6216b0. It may take a few minutes for all of github's web servers to update the content. Mike On 07/31/2013 09:54 PM, Eric Firing wrote: > On 2013/07/31 8:02 AM, Michael Droettboom wrote: >> The

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 08/01/2013 01:39 AM, Jason Grout wrote: On 7/31/13 8:17 PM, Michael Droettboom wrote: On 07/31/2013 10:18 PM, Jason Grout wrote: On 7/31/13 2:05 PM, Russell E. Owen wrote: As a result, binary installers now have to tell users to install these packages manually (as well as six and pyparsing)

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 7/31/13 8:17 PM, Michael Droettboom wrote: > On 07/31/2013 10:18 PM, Jason Grout wrote: >> On 7/31/13 2:05 PM, Russell E. Owen wrote: >>> As a result, binary installers now have to tell users to install >>> these packages manually (as well as six and pyparsing). >> I don't think six is mentioned

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 07/31/2013 10:18 PM, Jason Grout wrote: > On 7/31/13 2:05 PM, Russell E. Owen wrote: >> As a result, binary installers now have to tell users to install >> these packages manually (as well as six and pyparsing). > I don't think six is mentioned in the "What's new" note for 1.3.0. It > just deta

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 7/31/13 2:05 PM, Russell E. Owen wrote: > As a result, binary installers now have to tell users to install > these packages manually (as well as six and pyparsing). I don't think six is mentioned in the "What's new" note for 1.3.0. It just details that pyparsing, pytz, and dateutil are now de

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 2013/07/31 8:02 AM, Michael Droettboom wrote: > The layout has changed, but sidebar has not. Can you provide a > screenshot? Note, you can always visit the older version of the website > athttp://matplotlib.org/1.2.1 for direct comparison. The problem is that the new layout only works with a

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 7/31/13 11:02 AM, Michael Droettboom wrote: > The layout has changed, but sidebar has not. Can you provide a > screenshot? Note, you can always visit the older version of the website > at http://matplotlib.org/1.2.1 for direct comparison. I just realized I had the webpage zoomed in (apple/c

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 2013/07/31 11:12 AM, Russell E. Owen wrote: > All the interesting information about a build is printed at the > beginning and soon scrolls out of sight, so it's usually not obvious if > a build is missing something expected. I think we could collect that information and re-print it to the scree

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

In article <51f997f0.5060...@stsci.edu>, Michael Droettboom wrote: > On 07/31/2013 05:05 PM, Russell E. Owen wrote: > > In article <51f950cb.7060...@stsci.edu>, > > Michael Droettboom > > wrote: > > > >> On 07/31/2013 01:47 PM, Russell E. Owen wrote: > >>> In article <51f92f58.6020...@sts

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 07/31/2013 05:12 PM, Russell E. Owen wrote: > In article <51f950cb.7060...@stsci.edu>, > Michael Droettboom > wrote: > >> On 07/31/2013 01:47 PM, Russell E. Owen wrote: >>> In article <51f92f58.6020...@stsci.edu>, >>>Michael Droettboom >>>wrote: >>> I have tagged and uploaded

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 07/31/2013 05:05 PM, Russell E. Owen wrote: > In article <51f950cb.7060...@stsci.edu>, > Michael Droettboom > wrote: > >> On 07/31/2013 01:47 PM, Russell E. Owen wrote: >>> In article <51f92f58.6020...@stsci.edu>, >>>Michael Droettboom >>>wrote: >>> I have tagged and uploaded

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

In article <51f950cb.7060...@stsci.edu>, Michael Droettboom wrote: > On 07/31/2013 01:47 PM, Russell E. Owen wrote: > > In article <51f92f58.6020...@stsci.edu>, > > Michael Droettboom > > wrote: > > > >> I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to > >> all invol

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

In article <51f950cb.7060...@stsci.edu>, Michael Droettboom wrote: > On 07/31/2013 01:47 PM, Russell E. Owen wrote: > > In article <51f92f58.6020...@stsci.edu>, > > Michael Droettboom > > wrote: > > > >> I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to > >> all invol

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 07/31/2013 01:53 PM, Jason Grout wrote: > On 7/31/13 8:38 AM, Michael Droettboom wrote: >> I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to >> all involved! It was a long slog getting this release out, and I >> appreciate everyone's patience. >> >> Once we have binaries up

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 07/31/2013 01:47 PM, Russell E. Owen wrote: > In article <51f92f58.6020...@stsci.edu>, > Michael Droettboom > wrote: > >> I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to >> all involved! It was a long slog getting this release out, and I >> appreciate everyone's pati

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

On 7/31/13 8:38 AM, Michael Droettboom wrote: > I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to > all involved! It was a long slog getting this release out, and I > appreciate everyone's patience. > > Once we have binaries uploaded to SourceForge, I will make a formal > anno

Re: [matplotlib-devel] 1.3.0 final tagged and uploaded

In article <51f92f58.6020...@stsci.edu>, Michael Droettboom wrote: > I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to > all involved! It was a long slog getting this release out, and I > appreciate everyone's patience. > > Once we have binaries uploaded to SourceForge

[matplotlib-devel] 1.3.0 final tagged and uploaded

I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to all involved! It was a long slog getting this release out, and I appreciate everyone's patience. Once we have binaries uploaded to SourceForge, I will make a formal announcement in the usual channels. Mike ---