Today is the scheduled day for release candidate 1.2rc1.
We seem to be in really good shape. Thanks to everyone that has been
working so hard to squash bugs, particularly ones that turned out to be
bottomless rabbit holes.
We have a few outstanding issues, which I'll categorize below:
Hello,
Do you still accept pep8 cleaning up ? I've got a couple of important
deadlines coming up soon, but I might be able to clean up the whole code.
Thanks,
N
On 10 September 2012 18:00, Michael Droettboom md...@stsci.edu wrote:
Today is the scheduled day for release candidate 1.2rc1.
We
I'd certainly like to see that work continue, but I don't know if it's
worth holding up the release candidate for. We probably won't get it
out today given the other critical things yet to go in -- but once the
release candidate is cut, I'd prefer to be really conservative about
what changes
On 10/09/2012 17:00, Michael Droettboom wrote:
Today is the scheduled day for release candidate 1.2rc1.
We seem to be in really good shape. Thanks to everyone that has been
working so hard to squash bugs, particularly ones that turned out to be
bottomless rabbit holes.
We have a few
On 09/10/2012 12:49 PM, Mark Lawrence wrote:
My offer to test on Windows still holds. The question is test what?
Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then
different versions of Visual Studio are needed as detailed here
http://bugs.python.org/issue13210. I can't see
On Mon, Sep 10, 2012 at 5:00 PM, Michael Droettboom md...@stsci.edu wrote:
We have a few outstanding issues, which I'll categorize below:
Critical things that need just a little more work:
#1223dpi= for bitmaps not handled correctly
I don't believe this is release critical. It only
On 9/10/2012 10:08 AM, Michael Droettboom wrote:
On 09/10/2012 12:49 PM, Mark Lawrence wrote:
My offer to test on Windows still holds. The question is test what?
Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then
different versions of Visual Studio are needed as detailed
Hello,
This may be a silly question, but I'm wondering what happens in
Matplotlib rendering when there is a big Line2D object (say 10**7
points) added to an Axes, with *visibility set to false*.
Here is an tiny script meant to be run interactively (say with Python in
pylab mode) step by step :
