We should also update the checks for the version of Numpy. Expect a
pull request about this shortly.
Mike
On 11/12/2011 10:59 PM, Benjamin Root wrote:
On Saturday, November 12, 2011, John Ladasky
mailto:john_lada...@sbcglobal.net>> wrote:
> On Sat, 2011-11-12 at 20:08 -0600, Warren Weckes
Hi Ben and John,
> The doc page is wrong. There was suspicions of this recently with
> nextafter(), but no one knew when it was introduced in numpy. Now we know
> and I will update the page accordingly.
I ran into the same problem recently and discovered that nextafter() was
introduced in numpy
On Saturday, November 12, 2011, John Ladasky
wrote:
> On Sat, 2011-11-12 at 20:08 -0600, Warren Weckesser wrote:
>
>> By any chance do you have a file called 'numpy.py' in the directory
>> where you ran this? If so, rename that file and try again.
>
> Hi, Warren,
>
> No, there is no file named "n
On Sat, 2011-11-12 at 20:08 -0600, Warren Weckesser wrote:
> By any chance do you have a file called 'numpy.py' in the directory
> where you ran this? If so, rename that file and try again.
Hi, Warren,
No, there is no file named "numpy.py" in the directory with my test
programs, or anywhere o
On Saturday, November 12, 2011, John Ladasky
wrote:
> Two days ago I posted some questions about upgrading, and was pointed to
> the right resources by some readers who replied to me privately
> (thanks!). I am running Python 2.6 on an Ubuntu Linux 10.10 platform.
> The upgrade appeared to build
Two days ago I posted some questions about upgrading, and was pointed to
the right resources by some readers who replied to me privately
(thanks!). I am running Python 2.6 on an Ubuntu Linux 10.10 platform.
The upgrade appeared to build successfully, but I still have problems.
Line graphs appear
