This is a one-line ticket waiting for review, but is in pending state for
patchbots since it touches an "unsafe file" (sage-ipython). Would any of
you review?
http://trac.sagemath.org/ticket/19021
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
On Wed, Aug 19, 2015 at 12:30 PM, Travis Scrimshaw wrote:
> More of random thought, but would people be interested in adding a value to
> the builtin functions which says what a "good" default plot interval is,
> e.g., for sin(x) would be [-pi, pi] or [-2pi, 2pi] (and hope there's not too
> much b
More of random thought, but would people be interested in adding a value to
the builtin functions which says what a "good" default plot interval is,
e.g., for sin(x) would be [-pi, pi] or [-2pi, 2pi] (and hope there's not
too much bikeshedding)?
Best,
Travis
On Tuesday, August 18, 2015 at 10:
On Tuesday, 18 August 2015 22:56:45 UTC-7, Jori Mäntysalo wrote:
>
> On Tue, 18 Aug 2015, Dima Pasechnik wrote:
>
> >>> At http://trac.sagemath.org/ticket/17164 it seems that Sage 6.8 has
> not
> >>> support for vulnerable SSLv3 anymore. But it still seems to have - at
> >>> least on SageNB.
On Wednesday, August 19, 2015 at 11:51:49 AM UTC+2, David Roe wrote:
>
> Since you have an mpz_t, presumably you're writing in Cython.
Unfortunately, no. I'm improving Pynac to use gmp internally. But at some
time we must convert back. I completely missed set_from_mpz though.
With that I just nee
On Wednesday, August 19, 2015 at 12:36:07 PM UTC+2, vdelecroix wrote:
>
>
>
> On 19/08/15 12:31, Jean-Pierre Flori wrote:
> >
> >
> > On Wednesday, August 19, 2015 at 12:21:36 PM UTC+2, vdelecroix wrote:
> >>
> >> Note that all the solutions given will *copy* the mpz_t to the Integer.
> >>
On 19/08/15 12:31, Jean-Pierre Flori wrote:
On Wednesday, August 19, 2015 at 12:21:36 PM UTC+2, vdelecroix wrote:
Note that all the solutions given will *copy* the mpz_t to the Integer.
Is that what you want? It is also possible to avoid the copy if it is
worth it (i.e. you have a big integ
On Wednesday, August 19, 2015 at 12:21:36 PM UTC+2, vdelecroix wrote:
>
> Note that all the solutions given will *copy* the mpz_t to the Integer.
> Is that what you want? It is also possible to avoid the copy if it is
> worth it (i.e. you have a big integer).
>
And one shall not use PY_NEW bu
Note that all the solutions given will *copy* the mpz_t to the Integer.
Is that what you want? It is also possible to avoid the copy if it is
worth it (i.e. you have a big integer).
On 19/08/15 11:52, Jean-Pierre Flori wrote:
On Wednesday, August 19, 2015 at 11:19:30 AM UTC+2, Ralf Stephan w
On Wednesday, August 19, 2015 at 11:19:30 AM UTC+2, Ralf Stephan wrote:
>
> Given an mpz_t, how to most effectively create an Integer?
> The best I can come up with is through the string representation.
> Or, of course, by patching integer.pyx.
>
> Am I missing something?
>
> From Cython you can
Since you have an mpz_t, presumably you're writing in Cython. Then
you can do something like the following.
cdef mpz_t input
cdef Integer output = PY_NEW(Integer)
output.set_from_mpz(input)
Or something like
mpz_set(output.value, input).
David
On Wed, Aug 19, 2015 at 2:19 AM, Ralf Stephan wro
Given an mpz_t, how to most effectively create an Integer?
The best I can come up with is through the string representation.
Or, of course, by patching integer.pyx.
Am I missing something?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubs
On 2015-08-18 22:16, Jeroen Demeyer wrote:
- move the current low-level `sage -i` to, say, `sage -p` (which
automatically includes `sage -p -c -f` and remains consistent with
`sage -b` and `sage --docbuild`, so that we keep all the benefits of
(B)). Replace `sage -i` with `sage -p` in `s
13 matches
Mail list logo
