(resending to cython-devel list since my first attempt bounced)
On Tue, Dec 11, 2018, 11:56 Nathaniel Smith FYI – you should be aware that subinterpreters are poorly tested (AFAIK
> ceph is the third project to try using them, ever), not well supported in
> general, and there has even bee
On Mon, Nov 20, 2017 at 4:08 PM, Matthew Brett wrote:
> Hi,
>
> The manylinux1 docker image has just stopped supporting Python 2.6, so
> we can no longer build Python 2.6 wheels without putting some hacks on
> top:
>
> https://github.com/pypa/manylinux/pull/125#issuecomment-345770870
>
> Do y'all
On Jun 9, 2016 6:28 AM, "Elizabeth A. Fischer" <
elizabeth.fisc...@columbia.edu> wrote:
>
>
>
> On Thu, Jun 9, 2016 at 2:49 AM, Nathaniel Smith wrote:
>>
>> On Wed, Jun 8, 2016 at 10:37 PM, Elizabeth A. Fischer
>> wrote:
>> > Spack
On Wed, Jun 8, 2016 at 10:37 PM, Elizabeth A. Fischer
wrote:
> Spack gives you complete control over your compiler. This is important if
> you're building Python extensions, especially C++-based extensions, which
> must be built with the same compilers use to build Python.
Just to hopefully avo
Hi all,
Bug report here -- trying to edit some cython code in emacs just now,
emacs was repeatedly freezing until I'd hit C-g repeatedly. Made
things literally unusable -- I couldn't type characters into the
buffer. M-x toggle-debug-on-quit gives the backtrace:
Debugger entered--Lisp error: (quit
On Apr 11, 2016 06:23, "Erik Bray" wrote:
>
> On Mon, Apr 11, 2016 at 2:51 PM, Nathaniel Smith wrote:
> > Now, back to your example: Here the caller and callee are both compiled
into
> > the same shared library, so you don't want dllexport/dllimport at all,
y
On Apr 11, 2016 04:18, "Erik Bray" wrote:
>
> On Fri, Apr 8, 2016 at 5:49 PM, Nathaniel Smith wrote:
> > Can you give a tiny concrete example? My questions are basic enough
that I
> > feel like I'm missing something fundamental :-)
>
> Yes, I think you
Can you give a tiny concrete example? My questions are basic enough that I
feel like I'm missing something fundamental :-)
My first question is why you even need this, since AFAIK there are no cases
where it is correct to have a cython module dllexporting symbols that
appear in header files. This
the lengthy
build-from-source thing, but on CI servers they can instead run "pip
install [something]" to get a quick install? And what's wrong with the
current "pip install Cython --install-option="--no-cython-compile"?
On Mar 31, 2016 11:29 AM, "Stefan Behnel"
On Mar 31, 2016 6:40 AM, "Stefan Behnel" wrote:
>
> Jason Madden schrieb am 31.03.2016 um 15:13:
> > On Thursday, 31 March 2016 00:50:57 UTC-5, Matthew Brett wrote:
> >>
> >> On Wed, Mar 30, 2016 at 2:35 PM, Forest Gregg >> > wrote:
> >>> Thanks!
> >>>
> >>> Are there also plans to post Windows w
On Mon, Mar 28, 2016 at 4:04 PM, Emmanuel Gil Peyrot
wrote:
> On Mon, Mar 28, 2016 at 10:54:21AM -0700, Matthew Brett wrote:
> […]
>> I uploaded manylinux wheels for Cython 0.23.5.
>>
>> If you're on Linux, and you upgrade pip to 8.1.1 (current) you should
>> now get Cython via a manylinux wheel b
Hi all,
I wanted to announce a workshop I'm organizing at SciPy this year, and
invite you to attend!
What: A two-day workshop bringing together folks working on JIT/AOT
compilation in Python.
When/where: July 11-12, in Austin, Texas.
(This is co-located with SciPy 2016, at the same time as the
I have a few hundred files worth of Cython code, and I'd like to find
all instances where a variable/expression has a certain cdef class
type. (More specifically, I'd like to find all accesses to the cdef
fields of a particular cdef class, but even just finding all 'cdef
MYTYPE x" and "x" statement
, and if it's wrong then weird real bugs
will happen. Next question: how am I supposed to make this work? Maybe
I'm just missing it, but I can't find anything in the docs about how I
should tell cython that mtrand.pyx is really numpy.random.mtrand...?
-n
> On Sat, Mar 14, 2015
Hi all,
Can anyone shed any light on this?
https://github.com/numpy/numpy/issues/5680
-n
--
Nathaniel J. Smith -- http://vorpus.org
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
On Fri, Nov 7, 2014 at 5:13 PM, Ondrej Certik wrote:
> Hi,
>
> Cython sometimes fails to build on Travis for various projects. If it
> fails, it always ends with this error:
>
> https://gist.github.com/certik/08f16dd572170c17d956
I don't have any insight into the error, but for CI purposes I inst
On Sat, Jul 19, 2014 at 7:39 AM, Stefan Behnel wrote:
>
> Sturla Molden, 19.07.2014 00:36:
> > Robert Bradshaw wrote:
> >> It's not just the initial patch; I'm primarily worried about the
> >> maintenance burden
> >
> > And also, will it break utility code and binary blobs? It might not even be
>
On Fri, Jul 18, 2014 at 10:53 PM, Robert Bradshaw
wrote:
> On Fri, Jul 18, 2014 at 2:28 PM, Nathaniel Smith wrote:
>
>> On Fri, Jul 18, 2014 at 10:13 PM, Sturla Molden
>> wrote:
>> > Benjamin Lerman wrote:
>> >
>> >> Would cython ac
On Fri, Jul 18, 2014 at 10:13 PM, Sturla Molden wrote:
> Benjamin Lerman wrote:
>
>> Would cython accept to add such a copyright header on its files?
>
> You want to display the Apache licence in every single file, even those
> with utility C code?
It's annoying, but a pretty standard request.
On Sun, Jan 5, 2014 at 8:03 AM, Stefan Behnel wrote:
> Nathaniel Smith, 05.01.2014 02:07:
>> On 4 Jan 2014 22:01, "Stefan Behnel" wrote:
>>> Stefan Behnel, 04.01.2014 22:51:
>>>> Stefan Behnel, 04.01.2014 22:47:
>>>>> Nathaniel Smith, 04.01.
1, "Stefan Behnel" wrote:
> Stefan Behnel, 04.01.2014 22:51:
> > Stefan Behnel, 04.01.2014 22:47:
> >> Nathaniel Smith, 04.01.2014 18:36:
> >>> On 4 Jan 2014 17:07, "Robert Bradshaw" wrote:
> >>>> Yes, that'd be
raise SkipTest
> On Jan 4, 2014 9:54 AM, "Nathaniel Smith" wrote:
>>
>> On 4 Jan 2014 11:53, "Stefan Behnel" wrote:
>> >
>> > mark florisson, 03.01.2014 23:28:
>> > > On 3 January 2014 18:22, Stefan Behnel wrote:
>> > &
On 4 Jan 2014 11:53, "Stefan Behnel" wrote:
>
> mark florisson, 03.01.2014 23:28:
> > On 3 January 2014 18:22, Stefan Behnel wrote:
> >> I enabled the NumPy build for our Py3.3 test runs and while I was at
it, I
> >> got it to use the latest NumPy release 1.8. This made one of the tests
fail:
> >>
On Thu, Oct 3, 2013 at 5:03 PM, Robert Bradshaw wrote:
> On Thu, Oct 3, 2013 at 7:13 AM, Nathaniel Smith wrote:
>> On Thu, Oct 3, 2013 at 3:00 PM, Stefan Behnel wrote:
>>> Nathaniel Smith, 03.10.2013 14:35:
>>>> On Thu, Oct 3, 2013 at 1:23 PM, Stefan Behnel wrote
On Thu, Oct 3, 2013 at 3:00 PM, Stefan Behnel wrote:
> Nathaniel Smith, 03.10.2013 14:35:
>> On Thu, Oct 3, 2013 at 1:23 PM, Stefan Behnel wrote:
>>> Greg Ewing, 03.10.2013 14:10:
>>>> Robert Bradshaw wrote:
>>>>> cdef int *a, b, c, *d[3]
>>
On Thu, Oct 3, 2013 at 1:23 PM, Stefan Behnel wrote:
> Greg Ewing, 03.10.2013 14:10:
>> Robert Bradshaw wrote:
>>> cdef int *a, b, c, *d[3]
>>>
>>> is IMHO quite ugly but also adds a lot of complexity to the parser.
>>> What if instead we required
>>>
>>> cdef int* a
>>> cdef int b, c
On Sun, Jun 2, 2013 at 7:22 AM, Stefan Behnel wrote:
> mark florisson, 21.05.2013 15:32:
>> On 21 May 2013 14:14, Vitja Makarov wrote:
>>>
>>> def foo(int N):
>>> x = 1
>>> y = 0
>>> for i in range(N):
>>> x = x * 0.1 + y * 0.2
>>> y = x * 0.3 + y * 0.4
>>> print ty
On Tue, Apr 9, 2013 at 3:32 PM, mark florisson
wrote:
> On 9 April 2013 14:55, Nikita Nemkin wrote:
>> One alternative for code reuse in large Cython projects
>> could be packaging multiple modules into one shared library.
>
> We have 'include'! :) Seriously though, that wouldn't work well with t
On Tue, Apr 9, 2013 at 3:15 PM, Stefan Behnel wrote:
> Ok, got it now. That solves the distribution problem, assuming that all
> installed runtimes with a given version are equivalent. Basically, we'd
> move the code out and then cimport the stuff back that we need, which would
> then let the firs
On Tue, Apr 9, 2013 at 2:11 PM, Stefan Behnel wrote:
> Nathaniel Smith, 09.04.2013 15:00:
>> On 9 Apr 2013 13:50, "Stefan Behnel" wrote:
>>> Nathaniel Smith, 09.04.2013 14:25:
>>> There's also the problem of dependency hell and getting rid of old modul
On 9 Apr 2013 13:50, "Stefan Behnel" wrote:
>
> Nathaniel Smith, 09.04.2013 14:25:
> > On 9 Apr 2013 13:05, "mark florisson" wrote:
> >> However, the memoryview class is duplicated in every cython module,
which
> >> means a memoryview object
On 9 Apr 2013 13:05, "mark florisson" wrote:
> However, the memoryview class is duplicated in every cython module, which
means a memoryview object from another module will fail this check. This is
a general problem in Cython that could be worked around for memoryviews,
but in general the lack of a
On Mon, Apr 8, 2013 at 7:42 AM, Dag Sverre Seljebotn
wrote:
> I guess you have changed your implementation of PEP 3118 too slightly on the
> NumPy side? Is this undefined in the PEP or are you now not in strict
> adherence to it?
I just checked, and PEP 3118 just says that if a {C,F,ANY}_CONTIG
Hi all,
If you build current numpy master with
NPY_RELAXED_STRIDES_CHECKING=1 python setup.py install
then Cython code using ndarrays starts blowing up, e.g.:
# foo.pyx
def add_one(array):
cdef double[::1] a = array
a[0] += 1.
return array
>>> foo.add_one(np.ascontiguousarray(np.ar
On Thu, Feb 28, 2013 at 5:50 PM, Robert Bradshaw wrote:
> On Thu, Feb 28, 2013 at 7:13 AM, Sebastian Berg
> wrote:
>> Hey,
>>
>> Maybe someone here already saw it (I don't have a track account, or I
>> would just create a ticket), but it would be nice if Cython was more
>> forgiving about contigu
Hi Cythoneers,
Ralf just proposed this pull request for numpy, to unconditionally install
a warning filter to silence all "numpy.dtype size changed", "numpy.ufunc
size changed" warnings that Cython likes to spit out. See the links below
for details. Figured you should have a chance to comment, any
On Tue, Jul 17, 2012 at 9:55 PM, Christian Heimes wrote:
> Am 17.07.2012 18:55, schrieb Dag Sverre Seljebotn:
>> Read PEP 3118. Then implement __getbuffer__ and __releasebuffer__ in
>> your cdef class (don't know if it's documented but you can see example
>> in tests/run/buffer.pyx).
>
> The new b
On Mon, May 28, 2012 at 12:09 PM, mark florisson
wrote:
> On 28 May 2012 12:01, Nathaniel Smith wrote:
>> On Mon, May 28, 2012 at 11:55 AM, mark florisson
>> wrote:
>>> On 28 May 2012 11:41, Nathaniel Smith wrote:
>>>> On Mon, May 28, 2012 at 10:13 AM, mar
On Mon, May 28, 2012 at 11:55 AM, mark florisson
wrote:
> On 28 May 2012 11:41, Nathaniel Smith wrote:
>> On Mon, May 28, 2012 at 10:13 AM, mark florisson
>> wrote:
>>> On 28 May 2012 09:54, mark florisson wrote:
>>>> On 27 May 2012 23:12, Nathaniel Smith
On Mon, May 28, 2012 at 10:13 AM, mark florisson
wrote:
> On 28 May 2012 09:54, mark florisson wrote:
>> On 27 May 2012 23:12, Nathaniel Smith wrote:
>>> On Sun, May 27, 2012 at 10:24 PM, Dag Sverre Seljebotn
>>> wrote:
>>>> On 05/18/2012 10:30 AM, Dag Sv
On Sun, May 27, 2012 at 10:24 PM, Dag Sverre Seljebotn
wrote:
> On 05/18/2012 10:30 AM, Dag Sverre Seljebotn wrote:
>>
>> On 05/18/2012 12:57 AM, Nick Coghlan wrote:
>>>
>>> I think the main things we'd be looking for would be:
>>> - a clear explanation of why a new metaclass is considered too com
On Mon, May 14, 2012 at 3:23 PM, Dag Sverre Seljebotn
wrote:
> On 05/14/2012 01:34 PM, Stefan Behnel wrote:
>>
>> Dag Sverre Seljebotn, 13.05.2012 21:37:
>>>
>>> Anyway, thanks for the heads up, this seems to need a bit more work.
>>> Input
>>> from somebody more familiar with this corner of the C
On Sun, May 13, 2012 at 8:35 PM, Dag Sverre Seljebotn
wrote:
> On 05/12/2012 08:44 PM, Nathaniel Smith wrote:
>>
>> On Fri, May 11, 2012 at 2:25 PM, Dag Sverre Seljebotn
>> wrote:
>>>
>>> This comes from a refactor of the work on CEP 1000: A PEP proposal,
On Fri, May 11, 2012 at 2:25 PM, Dag Sverre Seljebotn
wrote:
> This comes from a refactor of the work on CEP 1000: A PEP proposal, with a
> hack for use in current Python versions and in the case of PEP rejection,
> that allows 3rd party libraries to agree on extensions to PyTypeObject.
>
> http:/
On Mon, Apr 30, 2012 at 9:49 PM, Dag Sverre Seljebotn
wrote:
> JIT is really the way to go. It is one thing that a JIT could optimize the
> case where you pass a callback to a function and inline it run-time. But
> even if it doesn't get that fancy, it'd be great to just be able to write
> somethi
On Sat, Apr 28, 2012 at 10:25 PM, mark florisson
wrote:
> On 28 April 2012 22:04, Nathaniel Smith wrote:
>> Was chatting with Wes today about the usual problem many of us have
>> encountered with needing to use some sort of templating system to
>> generate code ha
Was chatting with Wes today about the usual problem many of us have
encountered with needing to use some sort of templating system to
generate code handling multiple types, operations, etc., and a wacky
idea occurred to me. So I thought I'd through it out here.
What if we added a simple macro faci
On Mon, Apr 23, 2012 at 6:09 PM, Dimitri Tcaciuc wrote:
> I may be misuderstanding the intent here, but here it goes.
>
> If the main idea is to be able to call functions that are written in
> Julia or other languages, I think an effort to create an LLVM backend
> for Cython would go a long way to
On Thu, Apr 19, 2012 at 2:18 PM, Dag Sverre Seljebotn
wrote:
> On 04/19/2012 01:20 PM, Nathaniel Smith wrote:
>> @cython.inline
>> def square(x):
>> return x * x
>>
>> # .specialize is an un-standardized Cython interface
>> # square_double is an object i
On Thu, Apr 19, 2012 at 11:56 AM, Dag Sverre Seljebotn
wrote:
> I thought of some drawbacks of getfuncptr:
>
> - Important: Doesn't allow you to actually inspect the supported
> signatures, which is needed (or at least convenient) if you want to use an
> FFI library or do some JIT-ing. So an iter
On Wed, Apr 18, 2012 at 10:58 PM, Dag Sverre Seljebotn
wrote:
> On 04/18/2012 11:35 PM, Dag Sverre Seljebotn wrote:
>>
>> On 04/17/2012 02:24 PM, Dag Sverre Seljebotn wrote:
>>>
>>> On 04/13/2012 12:11 AM, Dag Sverre Seljebotn wrote:
Travis Oliphant recently raised the issue on the NumPy
On Tue, Apr 17, 2012 at 8:07 PM, Dag Sverre Seljebotn
wrote:
>
>
> Nathaniel Smith wrote:
>
>>On Tue, Apr 17, 2012 at 3:34 PM, Dag Sverre Seljebotn
>> wrote:
>>> On 04/17/2012 04:20 PM, Nathaniel Smith wrote:
>>>> Since you've set this up... I
On Tue, Apr 17, 2012 at 3:34 PM, Dag Sverre Seljebotn
wrote:
> On 04/17/2012 04:20 PM, Nathaniel Smith wrote:
>> Since you've set this up... I have a suggestion for something that may
>> be worth trying, though I've hesitated to propose it seriously. And
>> t
On Tue, Apr 17, 2012 at 1:24 PM, Dag Sverre Seljebotn
wrote:
> OK, here's the benchmark code I've written:
>
> https://github.com/dagss/cep1000
This is great!
> Assumptions etc.:
>
> - (Very) warm cache case is tested
>
> - I compile and link libmycallable.so, libmycaller.so and ./bench; with
On Tue, Apr 17, 2012 at 1:53 PM, Dag Sverre Seljebotn
wrote:
> On 04/17/2012 02:40 PM, Nathaniel Smith wrote:
>>
>> On Tue, Apr 17, 2012 at 12:54 PM, Dag Sverre Seljebotn
>> wrote:
>>>
>>> I don't believe doing interning right without a common depen
On Tue, Apr 17, 2012 at 12:54 PM, Dag Sverre Seljebotn
wrote:
> I don't believe doing interning right without a common dependency .so is all
> that easy. I'd love to see a concrete spec for it (e.g., if you use Python
> bytes in a dict in sys.modules['_nativecall'], the bytes objects could be
> de
On Sun, Apr 15, 2012 at 9:07 AM, Dag Sverre Seljebotn
wrote:
> On 04/15/2012 09:30 AM, Stefan Behnel wrote:
>>
>> Dag Sverre Seljebotn, 15.04.2012 08:58:
>>>
>>> Ah, Cython objects. Didn't think of that. More below.
>>>
>>> On 04/14/2012 11:02 PM, Stefan Behnel wrote:
thanks for writing
On Sun, Apr 15, 2012 at 9:15 AM, Dag Sverre Seljebotn
wrote:
> Do you really think it complicates the spec? SHA-1 is pretty standard, and
> Python ships with hashlib (the hashing part isn't performance critical).
>
> I prefer hashing to string-interning as it can still be done compile-time
> etc.
On Fri, Apr 13, 2012 at 11:22 PM, Dag Sverre Seljebotn
wrote:
>
>
> Robert Bradshaw wrote:
>
>>On Fri, Apr 13, 2012 at 2:24 PM, Nathaniel Smith wrote:
>>> On Fri, Apr 13, 2012 at 9:27 PM, Dag Sverre Seljebotn
>>> wrote:
>>>> Ah, I didn
On Fri, Apr 13, 2012 at 9:27 PM, Dag Sverre Seljebotn
wrote:
> Ah, I didn't think about 6-bit or huffman. Certainly helps.
>
> I'm almost +1 on your proposal now, but a couple of more ideas:
>
> 1) Let the key (the size_t) spill over to the next specialization entry if
> it is too large; and prepe
On Fri, Apr 13, 2012 at 12:59 PM, Dag Sverre Seljebotn
wrote:
> I'll go one further: Intern Python bytes objects. It's just a PyObject*, but
> it's *required* (or just strongly encouraged) to have gone through
>
> sig = sys.modules['_nativecall']['interned_db'].setdefault(sig, sig)
>
> Obviously i
On Fri, Apr 13, 2012 at 9:52 AM, Dag Sverre Seljebotn
wrote:
> On 04/13/2012 01:38 AM, Robert Bradshaw wrote:
>> Also, I'm not sure the type registration will scale, especially if
>> every callable type wanted to get registered. (E.g. currently closures
>> and generators are new types...) Where to
On Thu, Mar 29, 2012 at 5:25 PM, David Malcolm wrote:
> On Thu, 2012-03-29 at 11:10 +0100, mark florisson wrote:
>> > Then what happens if you have
>> >
>> > #ifdef FOO
>> > #define BAR 3
>> > #else
>> > #define BAR 4
>> > #endif
>> >
>> > ?? I'm not saying it is hard, but perhaps no longer comple
On Tue, Feb 21, 2012 at 8:02 PM, Robert Bradshaw
wrote:
> On Tue, Feb 21, 2012 at 9:19 AM, mark florisson
> wrote:
>> On 21 February 2012 04:42, Robert Bradshaw
>> wrote:
>>> Python bytecode -> LLVM is a great idea for creating ufuncs, the
>>> overhead of Cython + GCC is atrocious for stuff lik
On Oct 29, 2011 4:41 AM, "mark florisson" wrote:
> "
> Typed memoryviews can be used for efficient access to buffers. It is
> similar to the current buffer support, but has more features and
> cleaner syntax. A memoryview can be used in any context (function
> parameters, module-level, cdef class
On Wed, Jun 15, 2011 at 12:18 AM, Stefan Behnel wrote:
> Lisandro Dalcin, 14.06.2011 21:39:
>>
>> On 14 June 2011 16:20, Nathaniel Smith wrote:
>>>
>>> Hello Cython folks,
>>>
>>> This message (see below) is the second report I've gotten
On Jun 2, 2011 2:18 PM, "Dag Sverre Seljebotn"
wrote:
> If you only want this allowed in typedefs, then, being puristic, I think
that really a "fused type" is really different from a ctypedef, and that it
would warrant something like a new keyword.
>
> cdef fusedtype [list, dict, object] fused_t
11:46 AM, Dag Sverre Seljebotn
wrote:
> On 05/05/2011 08:42 PM, Nathaniel Smith wrote:
>>
>> On Thu, May 5, 2011 at 3:03 AM, Anand Patil
>> wrote:
>>>
>>> On May 4, 8:16 pm, Nathaniel Smith wrote:
>>>>
>>>> On Tue, May 3, 2011 at 10:10
On Mon, Apr 4, 2011 at 3:17 AM, Dag Sverre Seljebotn
wrote:
> * A simple and friendly solution that covers, perhaps, 80% of the cases,
> based on simply replacing range with prange.
This is a "merely" aesthetic objection, while remaining agnostic on
the larger discussion, but -- 'for i in prange
69 matches
Mail list logo
