Hi,
I'm new to this list and to Cython internals.
Reporting two recently found bugs:
1. Explicit cast fails unexpectedly:
ctypedef char* LPSTR
cdef LPSTR c_str = b"ascii"
c_str # Failure: Python objects cannot be cast from
pointers of primitive types
The problem i
On Fri, 2013-03-01 at 12:17 -0800, Robert Bradshaw wrote:
> On Fri, Mar 1, 2013 at 7:56 AM, Sebastian Berg
> wrote:
> > On Thu, 2013-02-28 at 23:25 -0800, Robert Bradshaw wrote:
> >> On Thu, Feb 28, 2013 at 11:12 AM, Nathaniel Smith wrote:
> >> > On Thu, Feb 28, 2013 at 5:50 PM, Robert Bradshaw
On Fri, Mar 1, 2013 at 7:56 AM, Sebastian Berg
wrote:
> On Thu, 2013-02-28 at 23:25 -0800, Robert Bradshaw wrote:
>> On Thu, Feb 28, 2013 at 11:12 AM, Nathaniel Smith wrote:
>> > On Thu, Feb 28, 2013 at 5:50 PM, Robert Bradshaw
>> > wrote:
>> >> On Thu, Feb 28, 2013 at 7:13 AM, Sebastian Berg
>
On Thu, 2013-02-28 at 23:25 -0800, Robert Bradshaw wrote:
> On Thu, Feb 28, 2013 at 11:12 AM, Nathaniel Smith wrote:
> > 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
2013/3/1 Stefan Behnel :
> Zaur Shibzukhov, 01.03.2013 10:46:
>> Could I help in order to include this in 19.0?
>
> I like pull requests. ;)
>
OK
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
Zaur Shibzukhov, 01.03.2013 10:46:
> Could I help in order to include this in 19.0?
I like pull requests. ;)
Stefan
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
2013/3/1 Stefan Behnel :
> ZS, 28.02.2013 21:07:
>> 2013/2/28 Stefan Behnel:
This allows to write unicode text parsing code almost at C speed
mostly in python (+ .pxd defintions).
>>>
>>> I suggest simply adding a constant flag argument to the existing function
>>> that states if checking
On Thu, Feb 28, 2013 at 10:54 PM, Zaur Shibzukhov wrote:
I think you could even pass in two flags, one for wraparound and one for
boundscheck, and then just evaluate them appropriately in the existing "if"
tests above. That should allow both features to be supported independent
>> Then it can simplify writing utility code in order to support
>> different optimization flags in other cases too.
>
> Usually, yes. Look at the dict iteration code, for example, which makes
> pretty heavy use of it.
>
> This may not work in all cases, because the C compiler can decide to *not*
>
Zaur Shibzukhov, 01.03.2013 07:54:
I think you could even pass in two flags, one for wraparound and one for
boundscheck, and then just evaluate them appropriately in the existing "if"
tests above. That should allow both features to be supported independently
in a fast way.
10 matches
Mail list logo