Dear sage-devel,
I have a question related to void pointers in Cython. I am wrapping a C++
library that has a function that accepts a function pointer and each time
it processes something it calls the passed function. The function being
passed is defined as
void hook(void *user_param ,
Yoo Jernej !
Not sure I understood what you wanted, but in
graphs/base/static_sparse_graph.pyx there is a Cython attribute which
points toward a Python list.
That's because we have to store the labels of each edge, and because that
label can be any python object.
If you look for
Hey Nathann,
yes yes, that's precisely what I was looking for:
cpdef void *user_param =PyObject * data
..
data = object PyObject * user_param
Thanks for the help
Jernej
On Fri, Dec 26, 2014 at 2:19 PM, Nathann Cohen nathann.co...@gmail.com
wrote:
Yoo Jernej !
Not sure I
Helloo everybody !
There is no pub in a radius of 40km of where I live, so I spend my evenings
rewriting Sage's developer manual.
Tonight I have two questions for you:
1) should we keep the Sage dev scripts in Sage ?
2) Should we keep it in the doc ?
yes yes, that's precisely what I was looking for:
cpdef void *user_param =PyObject * data
..
data = object PyObject * user_param
Thanks for the help
Don't forget the decref/incref stuff ! That's for Python's garbage
collector. Otherwise it will not know that the object is being used
I'm writing code for a new ring and my element is derived from
RingElement and the parent has category Rings.
Where can I find the code used by __eq__ ? (I searched now for some
while, but wasn't able to find it). In particular I'm interested in the
part which uses the coercion model.
Daniel
--
Hello,
Note that there is the googlegroups cython-users which might be a
better place for cython related questions.
Best
Vincent
2014-12-26 15:09 UTC+01:00, Nathann Cohen nathann.co...@gmail.com:
yes yes, that's precisely what I was looking for:
cpdef void *user_param =PyObject * data
Hi,
From this discussion
https://groups.google.com/d/topic/sage-devel/092yBmHfXQo/discussion
I guess that only __cmp__ is implemented, not __eq__.
Eric.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop
You shouldn't tinker with the Python reference counting system if it can be
avoided. Just make sure that the Python object that you want to pass to
your function is kept alive for as long as you are going to use the C
pointer to it.E.g. store it in an attribute of the Python object that is
On 2014-12-26, Nathann Cohen nathann.co...@gmail.com wrote:
--f46d043c7edc287181050b1f0d5c
Content-Type: text/plain; charset=UTF-8
Helloo everybody !
There is no pub in a radius of 40km of where I live, so I spend my evenings
rewriting Sage's developer manual.
Tonight I have two
By the way, I noticed some change in the behaviour of trac git server;
it seems that fetching u/foo/bar automatically results in
creation of a local branch trac/u/foo/bar.
Is this documented anywhere?
No idea. Really, these days I am trying to make the developer's manual
something I can
On Friday, December 26, 2014 6:23:43 PM UTC+1, Dima Pasechnik wrote:
By the way, I noticed some change in the behaviour of trac git server;
it seems that fetching u/foo/bar automatically results in
creation of a local branch trac/u/foo/bar.
No it doesn't. Local branches would be in the
Hello everybody,
Once again the patchbot blobs have disappeared from the trac website. It
seems to happen after every new beta release. What's happening behind the
scene ?
Frederic
Le mercredi 19 novembre 2014 10:04:34 UTC+1, Frédéric Chapoton a écrit :
Hello,
the patchbot seems to be
On 2014-12-26, Volker Braun vbraun.n...@gmail.com wrote:
--=_Part_5531_1685050387.1419616059330
Content-Type: multipart/alternative;
boundary==_Part_5532_1775001320.1419616059330
--=_Part_5532_1775001320.1419616059330
Content-Type: text/plain; charset=UTF-8
On Friday,
Bumpy bump.
http://trac.sagemath.org/ticket/17365
http://www.google.com/url?q=http%3A%2F%2Ftrac.sagemath.org%2Fticket%2F17365sa=Dsntz=1usg=AFQjCNHvTmGm10lUGkMxeJuWeXDU1cA2Hg
http://trac.sagemath.org/ticket/15649
I'd say by definition a git branch is what is listed by git branch.
Having said that, it is just a label for a commit. There are other kinds of
labels for commits, for example tags. Whenever you fetch (pull) something
from a remote a local copy (of the commits on the remote) is made, and they
Hey guys... I hate to interrupt your debugging but I had a question
about Sage-devel. Can I create a patch to remove that, in the end ?
Nathann
On 27 December 2014 at 03:45, Volker Braun vbraun.n...@gmail.com wrote:
I'd say by definition a git branch is what is listed by git branch. Having
Hey guys... I hate to interrupt your debugging but I had a question
about The Sage dev scripts. Can I create a patch to remove that, in
the end ?
Nathann
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop
If you do remove them don't forget to remove the associated documentation.
That is remove sage/dev but also doc/en/reference/dev and apply this little
patch too
https://github.com/cschwan/sage-on-gentoo/blob/master/sci-mathematics/sage-doc/files/sage-doc-dev.patch
François
On Saturday,
Very good. I guess the respective still open tickets
are wontfix then...
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To
20 matches
Mail list logo
