On Monday, January 9, 2017 at 11:46:18 AM UTC+1, Marc Mezzarobba wrote:
>
> Emmanuel Charpentier wrote:
> > Should this be discussed again, with a call for *VOTE* ?
>
> I don't think this is something that can be decided independently of
> other conventions (such as the semantics of equality ...
On 2017-01-09 23:11, Jean-Pierre Flori wrote:
I guess that to do that you need an argless constructor which does not
seem to be the case here.
Does the C++ class not have an argless constructor or is it just not
declared in the Cython file?
--
You received this message because you are subscr
On Monday, January 9, 2017 at 10:33:49 PM UTC+1, Jeroen Demeyer wrote:
>
> On 2017-01-09 16:45, Jean-Pierre Flori wrote:
> > I guess you want to free the memory allocated here:
> > *
> >
> https://github.com/sagemath/sage/blob/master/src/sage/libs/eclib/newforms.pyx#L112
>
>
> Alternatively
On 2017-01-09 16:45, Jean-Pierre Flori wrote:
I guess you want to free the memory allocated here:
*
https://github.com/sagemath/sage/blob/master/src/sage/libs/eclib/newforms.pyx#L112
Alternatively, instead of a pointer you could store the object itself in
the Python class. Then you wouldn't us
On Monday, January 9, 2017 at 9:08:46 PM UTC+1, Jean-Pierre Flori wrote:
>
> Isn't that the correct way to trigger Cytohn writin down an explicit call
> to the destructor?
>
Right, every new'ed C++ object should be del'ed somewhere in the program. I
misunderstood what you meant.
--
You receiv
On Mon, Jan 9, 2017 at 3:08 PM, Jean-Pierre Flori wrote:
>
>
> On Monday, January 9, 2017 at 7:03:57 PM UTC+1, Volker Braun wrote:
>>
>> On Monday, January 9, 2017 at 4:45:19 PM UTC+1, Jean-Pierre Flori wrote:
>>>
>>> You can just use the Python "del" operator and Cython should translate
>>> it t
On Sunday, January 8, 2017 at 3:43:27 AM UTC-5, Travis Scrimshaw wrote:
>
> Hey Joe,
>Sorry for the delayed response (I've been traveling the past few days).
>>
>>
>> Sorry for posting and then disappearing for a bit. Thanks for your
>> answers. I will be very happy to have your help with th
On Monday, January 9, 2017 at 7:03:57 PM UTC+1, Volker Braun wrote:
>
> On Monday, January 9, 2017 at 4:45:19 PM UTC+1, Jean-Pierre Flori wrote:
>>
>> You can just use the Python "del" operator and Cython should translate it
>> to a destructor call.
>>
>
> No, there is the following caveat when
I have seen a report for this in Gentoo
Against 2.6.0. I think it is because of the behaviour of the latest version of
Sed.
Francois
On 10/01/2017, at 1:53 AM, moritz
mailto:mor...@math.fu-berlin.de>> wrote:
Dear list,
I am trying to build sage from source on a thinkpad X240 running debian
On Monday, January 9, 2017 at 4:45:19 PM UTC+1, Jean-Pierre Flori wrote:
>
> You can just use the Python "del" operator and Cython should translate it
> to a destructor call.
>
No, there is the following caveat when cyclic Python references are
involved:
__dealloc__ is always called, but there
Thanks to both. I'll experiment with this. There's currently a
ticket already marked Positive Review on this interface (#10256) but
since that will have missed the 7.5 release it might make sense to add
to that ticket. Not sure.
John
On 9 January 2017 at 15:45, David Roe wrote:
> Python has a
Python has a __dealloc__ method, which is called when the object is garbage
collected. You can find examples by search_src.
On Jan 9, 2017 09:52, "John Cremona" wrote:
> In a reply to question 36225 at
> https://ask.sagemath.org/question/36225/memory-leak-with-modular-symbols/
> (my reply was de
I guess you want to free the memory allocated here:
*
https://github.com/sagemath/sage/blob/master/src/sage/libs/eclib/newforms.pyx#L112
You should add a __dealloc__ method to your class and free the memory there:
*
http://docs.cython.org/en/latest/src/userguide/special_methods.html#finalization
In a reply to question 36225 at
https://ask.sagemath.org/question/36225/memory-leak-with-modular-symbols/
(my reply was deleted by the system so you cannot read it) I offered
to try to help by asking here how to do somthign I don't know how to
do.
When you do
sage: E = EllipticCurve('11a1')
sage:
Hi Daniel,
thanks!
Best regards,
Simon
On 2017-01-09, Daniel Krenn wrote:
> On 2017-01-09 13:27, Simon King wrote:
>> Hi!
>>
>> My aim is to delete all those branches in my local git tree that are
>> merged in a specific branch, say, in "develop". I know that I can list
>> those branches by "gi
Dear list,
I am trying to build sage from source on a thinkpad X240 running debian
sid. When running make, I get the following error:
[mpir-2.7.2] mpn/.libs/preinv_divrem_1.o: In function
`__gmpn_preinv_divrem_1':
[mpir-2.7.2]
/home/mo/sage/local/var/tmp/sage/build/mpir-2.7.2/src/mpn/preinv_
On 2017-01-09 13:27, Simon King wrote:
> Hi!
>
> My aim is to delete all those branches in my local git tree that are
> merged in a specific branch, say, in "develop". I know that I can list
> those branches by "git branch --merged develop" and that I can delete
> branches by "git branch -d to_be_
Hi!
My aim is to delete all those branches in my local git tree that are
merged in a specific branch, say, in "develop". I know that I can list
those branches by "git branch --merged develop" and that I can delete
branches by "git branch -d to_be_deleted".
However, I lack experience in bash. So, I
I know that in linux, one approach that is sometimes taken is having the
software download the components "dirty" components separately (e.g. some
proprietary drivers and firmware, as well as fonts and codecs). Might it be
possible to take a similar approach?
Best,
Kosta
On Sunday, 1 January 2
Thanks!
On Monday, 9 January 2017 11:51:48 UTC+2, Jeroen Demeyer wrote:
>
> On 2017-01-09 10:44, Kosta wrote:
> > Sorry for the double post.
> > Is there a guideline for when it is safe to just "make" again after
> > upgrading the version in git
>
> Yes: "make" should always work, with one cav
Emmanuel Charpentier wrote:
> Should this be discussed again, with a call for *VOTE* ?
I don't think this is something that can be decided independently of
other conventions (such as the semantics of equality and comparisons and
the handling of inexactness). At the very least, I think someone wo
This is now
https://trac.sagemath.org/ticket/22158
--
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 post to this group,
On 2017-01-09 10:44, Kosta wrote:
Sorry for the double post.
Is there a guideline for when it is safe to just "make" again after
upgrading the version in git
Yes: "make" should always work, with one caveat: the documentation might
not build. So "make doc-clean && make" should always work. If n
Sorry for the double post.
Is there a guideline for when it is safe to just "make" again after
upgrading the version in git, versus "make distclean && make"?
Thanks in advance!
On Monday, 9 January 2017 01:00:34 UTC+2, Eric Gourgoulhon wrote:
>
> Hi,
>
> Le dimanche 8 janvier 2017 23:41:35 UTC+
Thanks! I'll get it.
On Monday, 9 January 2017 01:00:34 UTC+2, Eric Gourgoulhon wrote:
>
> Hi,
>
> Le dimanche 8 janvier 2017 23:41:35 UTC+1, Kosta a écrit :
>>
>> Hello,
>>
>> I'm trying to build 7.5.rc2 on the aforementioned platform. When getting
>> to pynac-0.7.3, I get an error (the first ob
25 matches
Mail list logo
