rock guys and how I will need Cython
in the future for my research...
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
On Fri, 2011-04-15 at 16:20 +0200, Yury V. Zaytsev wrote:
> To my surprise I discovered that my code started working and I don't
> have the buffer interface problem that I was facing before anymore.
I am under impression that the culprit was this commit:
ository? I would try to
set the watch flag and see if it works...
Thanks for you your hard work on Cython by the way!
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
t, especially now that I didn't have the full
picture. Maybe if you have access to the track just add a note that most
of the problems have been solved in the latest git master and it will be
fixed for good before the next release?
Thanks, Lisandro!
--
Sin
d of git pull
Or
$ git fetch origin
$ git reset --hard origin/master
which is what we used for our buildbot.
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
have nothing to lose).
> But it seems to me that the problem is somewhere in the jenkins configuration.
I didn't mean to say that there's no problem with Jenkins, just wanted
to suggest a possibly better way of updating the CI checkout :-)
--
Sincerely yours,
Yury V. Zaytsev
___
ny
sensible use of this information...
Hope that helps,
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
a dead-end since it's not gonna work with
PyPy, and a ctypes backend would be more preferable. Now there is a
possibility that it's no longer going to be the case...
Wow!
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
c
;__pyx_v_self->pEngine->OStack.top();
Am I doing something wrong? Is there any other way to achieve what I
want, other than writing custom C macros?
Thanks,
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
h syntax is used...
Hopefully, in the mean time, there is some other solution to the problem
that I have overlooked.
Z.
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
_5;
__pyx_t_5 = __pyx_v_self->pEngine->OStack.Token&();
whereas, I'd like to see generated this:
Token *__pyx_t_5;
__pyx_t_5 = __pyx_v_self->pEngine->OStack->top();
Any ideas?
--
Sincerely yours,
Yury V. Zaytsev
_
ideas?
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
;m also trying
to avoid using Python C API directly as much as possible.
> Won't list comprehensions work for you? They could potentially be adapted
> to presize the list.
I guess not.
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel ma
Python and/or NumPy that should be
installed for this feature to work? If yes, would it be possible to
include a compile-time check for that?
Unfortunately, I couldn't find anything regarding the minimally required
versions in the documentation...
Thanks!
--
Sincerely yours,
Yury V. Zaytsev
_
ed in Cython and how important is that? Shall I
create a bug report on the Trac? Is my only resort to test whether the
compiler supports -fno-strict-aliasing and use that?
Thanks!
--
Sincerely yours,
Yury V. Zaytsev
./cpp.c: In function ‘get_memview_MemoryView_5array_7memview___get__’:
.
nk you very much for this explanation, I just wanted to make sure
that this is unavoidable!
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
rror: zero length field name in format
Is this an intended behavior or Cython should have abstracted this
difference for me, and it can be considered a bug?
Thanks!
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@pytho
the verdict and your time, point
taken, it's not a bug.
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
I'm a floating point number
In [7]: bar(np.array( (1., 2., 3.), dtype=np.int )[2])
I'm an integer number
Thanks in advance for pointing me in the right direction!
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
On Mon, 2013-07-15 at 17:03 +0200, Yury V. Zaytsev wrote:
> However, when I run the same code from within Python, both checks work
> just fine. So is this a genuine bug in Cython, or, rather, NumPy is
> doing some black magic behind the scenes, that prevents
> Cython-compiled modules
On Mon, 2013-07-15 at 17:54 +0200, Yury V. Zaytsev wrote:
>
> 1) What's the best way to get Cython to generate (b) instead of (a)?
As it appears, it doesn't really matter, because I've realized that I
can import numpy without actually introducing a compile-time dependency
create an issue on the Trac or
GitHub?
Thanks!
--
Sincerely yours,
Yury V. Zaytsev
from libcpp.string cimport string
cdef string STR_BAD = "bad value"
# distutils: language = c++
from libcpp.string cimport string
cdef string STR_GOOD = "good value"
print("This should sho
an idea to extend (1) with the
ability to pass -D options to cython compiler, like:
cython -DHAVE_LIBFOO=1
Will any such pull request be accepted?
--
Sincerely yours,
Yury V. Zaytsev
Forwarded Message ----
From: Yury V. Zaytsev
Reply-to: cython-us...@googlegroups.com
To:
really means anything or not.
Thanks!
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
-DE
> starts on Monday).
Multiple fixes to array.extend()
https://github.com/cython/cython/pull/258
Not sure it qualifies, but to me it looks rather safe to be included and
Travis didn't complain about anything.
--
Sincerely yours,
Yury V. Zaytsev
___
Hi Stefan,
On Thu, 2013-10-10 at 08:49 +0200, Stefan Behnel wrote:
>
> Yury V. Zaytsev, 09.10.2013 15:01:
> > I've been playing with my Cython-generated extension on PyPy, trying to
> > load it through CPyExt, and, surprisingly, after a few fixes to PyPy, it
>
t;Number of OpenMP threads is '{}'!".format(x))
^
ompt.pyx:9:50: local variable 'x' referenced before assignment
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
es/pull/387
I would appreciate if you could chime in and vet it in the case that it
looks sane to you.
Thanks,
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
aster, but the resulting code might end up being a lot slower, so if
you then run a battery of tests that uses the module, you might end up
loosing way more than you gained by cutting down the compilation time.
--
Sincerely yours,
Yury V. Zaytsev
___
cyt
to work. Now, are there better approaches that I've overlooked?
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
.pyx:6:35: Template parameter not a type
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
On Wed, 10 Feb 2016, Yury V. Zaytsev wrote:
If the return type of a function is a normal type, then everything is
fine, but if it's a pointer or reference type, then Cython refuses to
compile it.
I've just found out that apparently this happens because Cython misparses
function
On Wed, 10 Feb 2016, Yury V. Zaytsev wrote:
Hope that helps to fix the problem for good though!
Apparently a separate, but related bug: when C++ class constructor is
templated, Cython fails to compile the code.
However, if I specify a return type (irrespectively of what type is), it
seems
rn.type.deduce_template_params(actual) for (pattern, actual) in
zip(func_type.args, arg_types)],
File "/home/zaytsev/src/cython/cython-git/Cython/Compiler/PyrexTypes.py",
line 3594, in deduce_template_params
elif self.empty_declaration_code() ==
actual.template_type.empty_declarati
more work into this :-)
Many thanks!
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
f there is much market for debug wheels, I'm currently
fetching the pre-built ones for the release version and building the debug
ones myself... which is something I can totally live with.
Thank you for your efforts!
--
Sincerely yours,
Yury V. Zaytsev
___
nteractive Python.
In [1]: import test1
In [2]: test1.Test
Out[2]: test1.Test
In [3]: import test2
In [4]: test2.Test
Out[4]: __main__.Test
I would appreciate any hints in the case that I'm deeply confused and
doing something obviously wrong...
--
Si
plained the root cause, I believe that there is a less
disgusting workaround one could possibly go for, what do you think?
class PyTest(namedtuple('Test', 'test')):
pass
--
Sincerely yours,
Yury V. Zaytsev
___
cython-dev
itory like `cython-issues`. Not sure
if it's worth it though...
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
u don't want to hear more stupid proposals, please let me know.
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
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.
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel ma
On Mon, 14 Nov 2016, James C. McPherson wrote:
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
On Fri, 17 Aug 2018, James C. McPherson wrote:
1.0 runs the risk of hitting "never install a 1.0 release" habits.
How about 2.9.0 ;-) ?
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 sid
or Py2 code and defaults to compiling with
Py3 syntax and semantics.
Sounds like an excellent plan, I like it!
--
Sincerely yours,
Yury V. Zaytsev
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
On 30. Jan 2020, at 03:52, John Skaller2 wrote:
>
> However the shared library extensions I generate will always be linked
> against a shared library. My build tech does not permit flat namespaces
> for dynamic linkage. I know you CAN get Python run time as a shared
> library on Debian based syst
45 matches
Mail list logo
