On 2015-01-30 05:28, William Stein wrote:
I'm just thinking it's a little depressing that we somehow broke Sage
this way... We should really switch to the proper argument parsing
code that John Palmieri wrote (like 4 years ago).
I guess you refer to
http://trac.sagemath.org/ticket/21
--
You
On Thu, Jan 29, 2015 at 8:29 PM, Francois Bissey
wrote:
> Should be solved in rc0 this is Trac #17685. I have been plagued by this for
> a while because my machine name is qcd-nzi3 - notice it contains "-n".
> Your script similarly has "-n" in it. Automatic fail.
Look at the code there:
-if [[ "
Thanks very much, François. I'll watch that ticket.
On Thursday, January 29, 2015 at 8:29:16 PM UTC-8, François wrote:
>
> Should be solved in rc0 this is Trac #17685. I have been plagued by this
> for
> a while because my machine name is qcd-nzi3 - notice it contains “-n”.
> Your script simil
On Thu, Jan 29, 2015 at 8:26 PM, Rob Beezer wrote:
> Genius. All three failing scripts have "-n" in the filename, and the
> renaming to "a.sage" allows the file to succeed. And the rest that do
> succeed do not have a "-n."
I'm just thinking it's a little depressing that we somehow broke Sage
t
Should be solved in rc0 this is Trac #17685. I have been plagued by this for
a while because my machine name is qcd-nzi3 - notice it contains “-n”.
Your script similarly has “-n” in it. Automatic fail.
François
> On 30/01/2015, at 17:12, Rob Beezer wrote:
>
> I have a short chunk of Sage code t
Genius. All three failing scripts have "-n" in the filename, and the
renaming to "a.sage" allows the file to succeed. And the rest that do
succeed do not have a "-n."
I'll make a ticket soon unless I hear that this is known already.
Thanks, William!
Rob
On Thursday, January 29, 2015 at 8:15
On Thu, Jan 29, 2015 at 8:12 PM, Rob Beezer wrote:
> I have a short chunk of Sage code that I am running from the command line.
> It produces errors with newer versions of Sage, but works as intended with
> older versions (producing a graphics file). Of about 20 such chunks, 3
> appear to be fail
I have a short chunk of Sage code that I am running from the command line.
It produces errors with newer versions of Sage, but works as intended with
older versions (producing a graphics file). Of about 20 such chunks, 3
appear to be failing. Is this a known problem? Should I make a ticket?
This is a bug report from a Sage user...
===
Hi,
I would like to report a bug in an interval graph recognition
procedure. I am using Sage online (cloud.sagemath.com).
Here is the code:
d='GvGNp?'
G = Graph(d)
i = G.is_interval(certificate = True)
g2 = graphs.IntervalGrap
This is now trac 17692
--
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, send email to sage-devel@goo
I confirm that it is broken with xterm in debian jessie.
--
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 g
On Thu, 29 Jan 2015 at 11:56AM -0800, Nils Bruin wrote:
> When I run sage, window size changes get ignored. Hence, window size
> changes aren't responded to, which is particularly annoying when looking at
> something in a pager: the pager will ruin the view when running in a window
> of a differ
On unix (and linux) there is a signal that get passed to processes
associated with a tty that is running in a window when the window gets
resized: SIGWINCH. Vanilla ipython (version 0.13.2 on my ancient fedora
19) processes that signal properly. You notice this when you change the
window size
On Thursday, January 29, 2015 at 10:52:32 AM UTC-8, Stefan wrote:
>
> No coercion is still faster than a fast coercion.
>
The line "1/self" occurs INSIDE the __invert__ special method of
> element.pyx.
>
> Should I open a ticket to replace that 1 by self.parent().one() ?
>
Yes, that seems like a
On Wednesday, January 28, 2015 at 4:45:54 PM UTC-6, Simon King wrote:
>
> Hi Stefan,
>
> On 2015-01-28, Stefan > wrote:
> > The question, now, is why the coercion system is invoked at all: I'm
> doing
> > arithmetic within my own ring. The culprit, I guess, is the expression
> > 1/self in el
Hello,
> actually, the issue is a licensing one. pip needs some SSL to fetch
> sources with https, so if Sage is built sith SSL support you won't have
> any problem. If openssl was a standard package, you will not have any
> problem either. Unfortunately, openssl is licensed in a way that it can
>
Hi Nathann,
actually, the issue is a licensing one. pip needs some SSL to fetch
sources with https, so if Sage is built sith SSL support you won't have
any problem. If openssl was a standard package, you will not have any
problem either. Unfortunately, openssl is licensed in a way that it can
not
Hello everybody,
I tried yesterday to install a Python package with 'pip', and ran into the
following problem (full taceback at the end):
~$ sage -pip install line-profiler
...
ImportError: cannot import name HTTPSHandler
Vincent sent me this link [1], and suggested the following procedure:
1)
18 matches
Mail list logo
