Hi Alan,
>
> I also had a follow up which crossed with yours. I think we pretty much
> agree now
> about what is going on, and only differ in that I would suggest doing the
> MinGW/MSYS testing first. But doing that after you have completed the MSVC
> case
> would also work if you prefer that
On 2013-10-18 07:27- Arjen Markus wrote:
> Hi Alan,
>
>> -Original Message-
>> From: Alan W. Irwin [mailto:[email protected]]
>>
> ...
>
>> Hi Arjen:
>>
>> My guess is the integrated python+numpy package version you have installed on
>> your computer combines so much from diffe
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:[email protected]]
>
...
> Hi Arjen:
>
> My guess is the integrated python+numpy package version you have installed on
> your computer combines so much from different versions of python and numpy
> that
> they are interf
On 2013-10-18 04:25- Arjen Markus wrote:
> Hi Alan,
> on my machine Python 2.7.5 is installed with Numpy 1.7 in a location
c:\Python27\Lib\site-packages\numpy\core\include as reported by
numpy.get_include(). So I think it is all correct. This installation
came with the territory so to say - i
rom: Alan W. Irwin [mailto:[email protected]]
> Sent: Friday, October 18, 2013 12:31 AM
> To: Arjen Markus
> Cc: Andrew Ross; PLplot development list
> Subject: RE: [Plplot-devel] Recent diff results for 32-bit Wine
>
> On 2013-10-17 19:51- Arjen Markus wrote:
>
>
On 2013-10-17 19:51- Arjen Markus wrote:
> Hi Alan,
>
> I am trying to get the Python bindings and examples ready under Windows so
> that I
> can compare the output with the C examples. However, I am getting a set of
> weird error messages.
> (I am not quite sure I have all the build tools r
mbol is part of Numpy pre-1.7 and it appears in
plplotcmodule.i but I do not know how to repair this.
I also do not know what the "void *" messages are all about.
Any suggestions, anyone?
Regards,
Arjen
> -Original Message-
> From: Alan W. Irwin [mailto:[email protected]
On 2013-10-16 08:00- Arjen Markus wrote:
> [...] I will have a look at the Python/Windows results, as I do not remember
> ever seeing
> such a long list of differing examples before.
Thanks in advance for that. It will be a big help to see exactly
which 32-bit platforms have this problem.
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:[email protected]]
>
> Good question. Actually extended precision (using 80-bits to store
> intermediate
> floating-point results) is just a part of the deal whenever you are running
> software on
> Intel hardware. It'
On 2013-10-15 06:46- Arjen Markus wrote:
> Hi Alan,
>
>> -Original Message-
>> From: Alan W. Irwin [mailto:[email protected]]
>
> ...
>>
>> In sum, there is an issue with our Python results on 32-bit Windows that
>> needs to be
>> confirmed also on 32-bit Linux. All theoretic
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:[email protected]]
...
>
> In sum, there is an issue with our Python results on 32-bit Windows that
> needs to be
> confirmed also on 32-bit Linux. All theoretical analysis and practical gdb
> results I can
> come up w
Hi Andrew:
Happy (Canadian) Thanksgiving!
Here are some recent test results I have obtained on my 32-bit
MinGW/MSYS/Wine platform using the build_projects approach.
c++
Missing examples:
Differing postscript output :
Missing stdout :
Differing stdout
12 matches
Mail list logo
