On 4/08/17 04:10 am, Matthew Brett wrote:
Hi,
On Thu, Aug 3, 2017 at 4:04 PM, Matthew Brett <matthew.br...@gmail.com> wrote:
Hi,
On Thu, Aug 3, 2017 at 2:12 PM, Andy <t3k...@gmail.com> 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 <module>
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
