I created a new component "plotting" on Trac. If anybody would like to
become owner of such tickets (meaning you will get all emails from
tickets with this component), let me know. Currently, there is no owner.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscrib
On 4/19/12 2:18 AM, Jeroen Demeyer wrote:
I created a new component "plotting" on Trac. If anybody would like to
become owner of such tickets (meaning you will get all emails from
tickets with this component), let me know. Currently, there is no owner.
How is this different than the graphics
On 2012-04-19 09:30, Jason Grout wrote:
> On 4/19/12 2:18 AM, Jeroen Demeyer wrote:
>> I created a new component "plotting" on Trac. If anybody would like to
>> become owner of such tickets (meaning you will get all emails from
>> tickets with this component), let me know. Currently, there is no
On 4/19/12 3:39 AM, Jeroen Demeyer wrote:
On 2012-04-19 09:30, Jason Grout wrote:
On 4/19/12 2:18 AM, Jeroen Demeyer wrote:
I created a new component "plotting" on Trac. If anybody would like to
become owner of such tickets (meaning you will get all emails from
tickets with this component), le
On 2012-04-19 11:40, Jason Grout wrote:
> On 4/19/12 3:39 AM, Jeroen Demeyer wrote:
>> On 2012-04-19 09:30, Jason Grout wrote:
>>> On 4/19/12 2:18 AM, Jeroen Demeyer wrote:
I created a new component "plotting" on Trac. If anybody would like to
become owner of such tickets (meaning you wi
Also removed components:
* debian_package
* dsage (0 tickets)
* msvc (0 tickets)
* sage-mode (0 tickets)
Then there are a few very specific components like "fractals" which have
tickets but should probably be removed also and be recategorized in a
different component.
--
To post to this group, s
Hi,
> > Forget about the critical ones. Here are the ones listed as blockers:
> >
> > #12849 The argspecs is broken in the Sphinx documentation > >
> > [...]
>
> I put it myself as a blocker, since it impairs a large part of Sage
> HTML doc. I'm currently investigating on
Hi,
I get the following error while trying to install git from
sage-optional packages. The error seems to be in one of the python
library files (os.py) and is a syntax error -
File "/compute/imsc9/rajeev/bin/sage-4.8/local/lib/python/os.py", line 758
bs = b""
^
SyntaxError: invali
Please review blocker ticket #12857: it splits the file
sage/plot/plot.py in two files: graphics.py containing the Graphics and
GraphicsArray classes, plot.py containing the actual plot() commands.
This split was needed because doctesting plot.py took much longer than
any other file and doctest ti
On 2012-04-19, Rajeev Singh wrote:
> Hi,
>
> I get the following error while trying to install git from
> sage-optional packages. The error seems to be in one of the python
> library files (os.py) and is a syntax error -
>
> File "/compute/imsc9/rajeev/bin/sage-4.8/local/lib/python/os.py", line 7
The b"" is a string with the Python 3 byte-prefix. In Python 2, version
2.6+ this is a noop for Python 3 compatibility. In Python versions older
than 2.6, this is an error.
Conclusion: You are running an old Python interpreter, in particular not
the one that is part of Sage. Hence it breaks.
On Apr 19, 5:40 am, Jason Grout wrote:
> On 4/19/12 3:39 AM, Jeroen Demeyer wrote:
>
> > On 2012-04-19 09:30, Jason Grout wrote:
> >> On 4/19/12 2:18 AM, Jeroen Demeyer wrote:
> >>> I created a new component "plotting" on Trac. If anybody would like to
> >>> become owner of such tickets (meanin
On 19 Apr., 12:09, Jeroen Demeyer wrote:
> Also removed components:
> * debian_package
> * dsage (0 tickets)
> * msvc (0 tickets)
> * sage-mode (0 tickets)
>
> Then there are a few very specific components like "fractals" which have
> tickets but should probably be removed also and be recategorize
On 19 Apr., 20:59, kcrisman wrote:
> On Apr 19, 5:40 am, Jason Grout wrote:
> > On 4/19/12 3:39 AM, Jeroen Demeyer wrote:
> > > On 2012-04-19 09:30, Jason Grout wrote:
> > >> On 4/19/12 2:18 AM, Jeroen Demeyer wrote:
> > >>> I created a new component "plotting" on Trac. If anybody would like to
On 19 Apr., 05:33, Stephen Montgomery-Smith
wrote:
> I think I have found the problem with sympow. It is nothing to do with
> elliptic curves. It is simply a malloc/free error.
>
> In util.c there is a function free_data, which frees TACKS[0]. TACKS[0]
> is meant to be allocated in disk.c, but
Given that it claims to be about both research and education usage, I'm
forwarding this to the other relevant Google groups. Nice find!
On Thursday, April 19, 2012 2:11:19 PM UTC-4, LFS wrote:
>
> Hopefully doing this correctly since not exactly a "question". Just wanted
> to make sure this gro
On 17 Apr., 23:30, David Roe wrote:
> Patching zn_poly in Sage sounds good to me
I could include such a patch into the zn_poly spkg at
http://trac.sagemath.org/sage_trac/ticket/12433
-leif
> On Tue, Apr 17, 2012 at 17:25, François Bissey
> wrote:
> > On Tue, 17 Apr 2012 16:56:52 David R
On 2012-04-19 21:05, leif wrote:
> Can you rename the porting "subcomponents" as suggested?
No, but maybe somebody who knows more about Trac can.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googleg
On 18 Apr., 00:44, Bill Hart wrote:
> At the present moment flint 2.3 does not use zn_poly.
zn_poly's 'configure' has some '--use-flint' option, but we currently
don't use that either.
-leif
> We may be incorporating some code from zn_poly in flint 2.3 in the
> future, but will not need to hav
That would be great.
David
On Thu, Apr 19, 2012 at 13:27, leif wrote:
> On 17 Apr., 23:30, David Roe wrote:
> > Patching zn_poly in Sage sounds good to me
>
> I could include such a patch into the zn_poly spkg at
>
> http://trac.sagemath.org/sage_trac/ticket/12433
>
>
> -leif
>
> > On Tue,
On 19 Apr., 22:34, Jeroen Demeyer wrote:
> On 2012-04-19 21:05, leif wrote:
> Can you rename the porting "subcomponents" as suggested?
>
> No, but maybe somebody who knows more about Trac can.
Not me. Haven't even tried, but presumably needs some SQL statement
to change the fields of all tickets
I can probably do it, if we decide on a list of changes we want to make.
David
On Thu, Apr 19, 2012 at 13:44, leif wrote:
> On 19 Apr., 22:34, Jeroen Demeyer wrote:
> > On 2012-04-19 21:05, leif wrote:
> > Can you rename the porting "subcomponents" as suggested?
> >
> > No, but maybe somebody w
The following snippet appears to exhibit a minor bug in base_ring:
sage: F.=FiniteField(5^6)
sage: z.base_ring()
Finite Field of size 5
sage: a.parent()
Finite Field in z of size 5^6
According to the documentation, base_ring() "Returns the base ring of this
element's parent (if that makes sense)
Hi,
On Fri, Apr 20, 2012 at 8:02 AM, Andrew Mathas wrote:
> The following snippet appears to exhibit a minor bug in base_ring:
>
> sage: F.=FiniteField(5^6)
> sage: z.base_ring()
> Finite Field of size 5
> sage: a.parent()
> Finite Field in z of size 5^6
>
> According to the documentation, base_r
I don't think that should happen because I'm just giving the following
command on terminal -
sage -i git-1.7.9.4
I am using sage-4.8. I get the same error on two computers (one
running SuseLinux and another running Debian).
Rajeev
On Thu, Apr 19, 2012 at 11:48 PM, Volker Braun wrote:
> The b"
On Thursday, April 19, 2012 8:25:15 PM UTC-7, Rajeev wrote:
>
> I don't think that should happen because I'm just giving the following
> command on terminal -
>
> sage -i git-1.7.9.4
>
> I am using sage-4.8. I get the same error on two computers (one
> running SuseLinux and another running Debian
On 20 Apr., 05:25, Rajeev Singh wrote:
> I don't think that should happen because I'm just giving the following
> command on terminal -
>
> sage -i git-1.7.9.4
>
> I am using sage-4.8. I get the same error on two computers (one
> running SuseLinux and another running Debian).
What does
$ sage --
On Thursday, April 19, 2012 9:23:47 PM UTC-7, leif wrote:
>
> On 20 Apr., 05:25, Rajeev Singh wrote:
> > I don't think that should happen because I'm just giving the following
> > command on terminal -
> >
> > sage -i git-1.7.9.4
> >
> > I am using sage-4.8. I get the same error on two com
On 20 Apr., 06:23, leif wrote:
> On 20 Apr., 05:25, Rajeev Singh wrote:
>
> > I don't think that should happen because I'm just giving the following
> > command on terminal -
>
> > sage -i git-1.7.9.4
P.S.: You should try the git-1.7.9.4.p1.spkg
-leif
--
To post to this group, send an emai
On 20 Apr., 06:27, John H Palmieri wrote:
> On Thursday, April 19, 2012 9:23:47 PM UTC-7, leif wrote:
>
> > On 20 Apr., 05:25, Rajeev Singh wrote:
> > > I don't think that should happen because I'm just giving the following
> > > command on terminal -
>
> > > sage -i git-1.7.9.4
>
> > > I am usin
That is here: http://trac.sagemath.org/sage_trac/ticket/12707
On Friday, April 20, 2012 12:31:04 PM UTC+8, leif wrote:
>
>
>
> On 20 Apr., 06:23, leif wrote:
> > On 20 Apr., 05:25, Rajeev Singh wrote:
> >
> > > I don't think that should happen because I'm just giving the following
> > > comm
Hmm...
keshav@sage ~ $ mkdir bin
keshav@sage ~ $ cat - > bin/python
#!/bin/sh
echo "You are likely to be eaten by a grue"
keshav@sage ~ $ chmod a+x bin/python
keshav@sage ~ $ export PATH="/home/keshav/bin:$PATH"
keshav@sage ~ $ ./sage/sage -i ./git-1.7.9.4.p1.spkg | grep grue
keshav@sage ~ $
So
On 20 Apr., 06:35, leif wrote:
> On 20 Apr., 06:27, John H Palmieri wrote:
>
>
>
>
>
>
>
>
>
> > On Thursday, April 19, 2012 9:23:47 PM UTC-7, leif wrote:
>
> > > On 20 Apr., 05:25, Rajeev Singh wrote:
> > > > I don't think that should happen because I'm just giving the following
> > > > comma
Uh... I'm not sure why Google Groups just quoted John's message five times,
but sorry about that...
-Keshav
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit th
On 20 Apr., 06:49, Keshav Kini wrote:
> Uh... I'm not sure why Google Groups just quoted John's message five times,
> but sorry about that...
In this case not that bad, as I completely missed his original post.
>8)
I'm pretty sure Google swallowed it for me in the first place (old web
interface
D'oh:
keshav@sage ~ $ grep -r '/python' git-1.7.9.4.p1
git-1.7.9.4.p1/src/Makefile:PYTHON_PATH = /usr/bin/python
git-1.7.9.4.p1/src/Makefile:PYTHON_PATH = /usr/local/bin/python
git-1.7.9.4.p1/src/git_remote_helpers/Makefile:PYTHON_PATH =
/usr/local/bin/python
git-1.7.9.4.p1/src/gi
Er, not patch the makefile, but actually just exporting some environment
variables should be sufficient.
-Keshav
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, vis
On 20 Apr., 06:48, leif wrote:
> On 20 Apr., 06:35, leif wrote:
> > On 20 Apr., 06:27, John H Palmieri wrote:
> > > On Thursday, April 19, 2012 9:23:47 PM UTC-7, leif wrote:
> > > > On 20 Apr., 05:25, Rajeev Singh wrote:
> > > > > I don't think that should happen because I'm just giving the fol
OK, a new SPKG is up in my homedir on boxen. Once ticket #12707 is
accepted, the SPKG will be on the official server, and one should be
able to install it with `sage -i git`, but for now, please test with
$ cd /tmp
$ wget http://boxen.math.washington.edu/home/keshav/files/git-1.7.10.spkg
$ sage -
Alex Ghitza writes:
> On Fri, Apr 20, 2012 at 8:02 AM, Andrew Mathas
> wrote:
>> The following snippet appears to exhibit a minor bug in base_ring:
>>
>> sage: F.=FiniteField(5^6)
>> sage: z.base_ring()
>> Finite Field of size 5
>> sage: a.parent()
>> Finite Field in z of size 5^6
>>
>> Accordin
40 matches
Mail list logo
