[Cython] q re environment for successful test suite run

2016-11-12 Thread James C. McPherson 


Hi all,
I'm building Cython 0.24.1 for Solaris and I'm finding it
difficult to get the test suite to run successfully.

I've tried several different versions of gcc (4.9, 5.3, 5.4)
and Solaris Studio (12.4), but to no avail.

For starters, here's the first lot of errors from gcc 5.4
in 32bit mode against python2.7:


warning: 
BUILD/inline/_cython_inline_d1a30658ebea82281640c5ea0e1db57e.pyx:6:4: 
Unreachable code
warning: 
BUILD/inline/_cython_inline_121fdd47c08e20991f90b2566f9a1705.pyx:6:4: 
Unreachable code
warning: 
BUILD/inline/_cython_inline_a938867fe92f83497d786ebdab9e4e1d.pyx:7:4: 
Unreachable code
BUILD/inline/_cython_inline_a938867fe92f83497d786ebdab9e4e1d.c: In 
function '__pyx_pf_5numpy_7ndarray___getbuffer__':
BUILD/inline/_cython_inline_a938867fe92f83497d786ebdab9e4e1d.c:1522:50: 
error: 'NPY_C_CONTIGUOUS' undeclared (first use in this function)
   __pyx_t_2 = ((!(PyArray_CHKFLAGS(__pyx_v_self, NPY_C_CONTIGUOUS) != 
0)) != 0);

  ^
BUILD/inline/_cython_inline_a938867fe92f83497d786ebdab9e4e1d.c:1522:50: 
note: each undeclared identifier is reported only once for each function 
it appears in
BUILD/inline/_cython_inline_a938867fe92f83497d786ebdab9e4e1d.c:1586:50: 
error: 'NPY_F_CONTIGUOUS' undeclared (first use in this function)
   __pyx_t_2 = ((!(PyArray_CHKFLAGS(__pyx_v_self, NPY_F_CONTIGUOUS) != 
0)) != 0);

  ^

When you run the test suite, what combination of compiler(s),
python interpreter(s) and CFLAGS/CXXFLAGS are used?


Thankyou in advance,
James C. McPherson
--
Oracle
Systems / Solaris / Core
https://www.jmcpdotcom.com/blog
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel

Re: [Cython] q re environment for successful test suite run

2016-11-13 Thread James C. McPherson 

On 13/11/16 06:58 pm, Yury V. Zaytsev wrote:

On Mon, 7 Nov 2016, James C. McPherson wrote:


  __pyx_t_2 = ((!(PyArray_CHKFLAGS(__pyx_v_self, NPY_F_CONTIGUOUS) !=
  ^

When you run the test suite, what combination of compiler(s),
python interpreter(s) and CFLAGS/CXXFLAGS are used?


So, do you have NumPy installed for this Python version? This particular
error seems to result from a NumPy identifier defined in the respective
header files, which you don't seem to have available.


Hi Yury,
On each of the test machines I've tried, I've got numpy
v1.9 installed.

I built Cython with the NumPy deprecation per
http://docs.cython.org/en/latest/src/reference/compilation.html#configuring-the-c-build

- should I have ignored it?


Thankyou,
James C. McPherson
--
Oracle
Systems / Solaris / Core
https://www.jmcpdotcom.com/blog
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel

Re: [Cython] Preparations for Cython 0.26.1 and 0.27

2017-08-03 Thread James C. McPherson 

On  4/08/17 04:10 am, Matthew Brett wrote:

Hi,

On Thu, Aug 3, 2017 at 4:04 PM, Matthew Brett  wrote:

Hi,

On Thu, Aug 3, 2017 at 2:12 PM, Andy  wrote:

One more thing: If there was a nightly wheel like for scipy and numpy,
we could run CI with Cython master. That might lead to finding issues
earlier.
We probably don't want to build cython from source on CI, as I expect that
would
take too much time.


That's a good idea - I will set that up, and email back here with details.


OK - I have set that up, wheels building on the "daily" branch here:

https://travis-ci.org/MacPython/cython-wheels/branches

But, I'm a bit worried by the pre-release naming scheme, because the
built wheel has name of form "Cython-0.26.1a0-cp..." . Can I ask -
where does the "1a0" come from?  Can it be used to select the most
recent pre-release wheel?  I mean, if we build a wheel from a later
commit, will pip find the later wheel before this one?


I'm pretty sure that the '1a0' comes from changeset hash,
to reflect however many changes this build has pulled in
which are ahead of or behind trunk.

Also, from reading 
https://travis-ci.org/MacPython/cython-wheels/jobs/255434019

I'm not entirely sure that it's all setup correctly, given
the prevalence of messages such as these:



ERROR:root:code for hash blake2b was not found.
Traceback (most recent call last):
  File "/opt/cp36m/lib/python3.6/hashlib.py", line 243, in 
globals()[__func_name] = __get_hash(__func_name)
  File "/opt/cp36m/lib/python3.6/hashlib.py", line 119, in 
__get_openssl_constructor

return __get_builtin_constructor(name)
  File "/opt/cp36m/lib/python3.6/hashlib.py", line 113, in 
__get_builtin_constructor

    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type blake2b


James C. McPherson
--
Oracle
Systems / Solaris / Core
https://www.jmcpdotcom.com/blog
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel

Re: [Cython] Cython 0.29 – or 29.0 ?

2018-08-17 Thread James C. McPherson 



1.0 runs the risk of hitting "never install a 1.0 release" habits.

Jumping to 29.0 would not, imnsho, be such an issue because people
are used to the rapid cadence of Firefox, Thunderbird and Chrome
releases. The flip side of 29.0 would be the question "when are you
announcing your LTS version?"

James


On 08/16/18 08:48 AM, Robert Bradshaw wrote:
If we're going to ditch the 0.x, I'd go for 1.0 as well. I'm a huge fan of 
semantic versioning.


The primary reasons we kept the 0.x scheme were that

* We wanted full compatibility with CPython (we're nearly there, or at 
least it's safe to say the differences are on par with those between 
different versions and implementations of Python), and
* We wanted the flexibility to possibly jettison archaic features of the 
language or otherwise clean things up.


It's worth revisiting to see if either of these are still relevant (*and* 
likely to be worked on in the near future).




On Wed, Aug 15, 2018 at 10:40 PM, Jeroen Demeyer > wrote:


I vote for 1.0

Version 29.0 sounds too much like marketing.

___
cython-devel mailing list
cython-devel@python.org 
https://mail.python.org/mailman/listinfo/cython-devel





___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel




--
Oracle
Systems / Solaris / Core
Solaris WOS Tech Lead
https://www.jmcpdotcom.com/blog
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel