[sage-devel] Re: Where is the long_element (or w0) method of Coxeter groups gone?

[Travis Scrimshaw]

Hey Jean-Philippe,
   The current default Coxeter group is to use the reflection 
representation for general Coxeter groups and I didn't include specialized 
methods for getting something like the longest element. Before, you were 
secretly working with an instance of WeylGroup, which is why the method for 
getting the longest element is no longer there. However, the category isn't 
set right; this is now http://trac.sagemath.org/ticket/16630.

Best,
Travis


On Tuesday, July 8, 2014 7:43:31 AM UTC-7, jplab wrote:
>
> Hi,
>
> I had some older code using Coxeter groups. Since I was running the code 
> on machines with different version of Sage, I was handling manually if 
> whether it had "CoxeterGroup" or not (I used WeylGroup when needed). 
>
> Now I'm rebasing my code to the latest version of Sage, and to my 
> surprise, there seems not to have a method to get the longest element 
> anymore?
>
> For WeylGroup, I can get .longest_element_hardcoded(). Nevertheless, I do 
> not want to work with WeylGroups since I also need several things about 
> Coxeter groups.
>
> What happened to the method formerly known as .w0?
>
> Thank you,
> Jean-Philippe
>
>

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Please review #/16626

[Volker Braun]

This adds a check to the doctest framework to raise an error for explicit 
line numbers

   sage: raise_warning()
   doctest:1234: Warning: this is a warning   # not cool! depends on source 
line number


-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] build system : a (smallish) bug when adding/updatng a package.

[Emmanuel Charpentier]

The current (as of -.3beta5) sage-fix-pkg-checksums munches the 
package-version and checksums.ini files of external packages, especially 
when used naïvely as suggested in the Developer's guide 
.

This is now Trac#16629 , for which a 
first solution is proposed, which awaits your review and discussion :

I spotted also a couple of possible enhancements, whic now presents 
suggestions to user, mut may automagically carry the necessary fixes. This 
has to be discussed by people with more knowledge of sage's build system 
than I have.

HTH,

--
Emmanuel Charpentier

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: strange (to me) doctest failure

[Eric Gourgoulhon]

Le mardi 8 juillet 2014 10:58:06 UTC+2, Martin Albrecht a écrit :
>
> Sure, this was about fixing a bug introduced in said ticket (which I now 
> found 
> :)


Sorry, I completely misunderstood your post !
Good that you found the bug. 

Eric.

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Problem installing sagecell

[kcrisman]

On Tuesday, July 8, 2014 11:41:20 AM UTC-4, kcrisman wrote:
>
> I'm trying with the new package but I still obtain error. I have tried 
>> your solution but:
>>
>> *sagecell@kimba:~/sage/sagecell$ ../sage -sh -c "make -B"*
>> *if git submodule status | grep -q ^[+-]; then git submodule update 
>> --init > /dev/null; fi*
>> *python -c "import urllib; 
>> urllib.urlretrieve('http://code.jquery.com/jquery-2.1.0.min.js 
>> ', 'static/jquery.min.js')"*
>> *gcc -o submodules/jsmin-bin submodules/jsmin/jsmin.c*
>> *r.js -o static/require/main.js 
>> appDir=/home/sagecell/sage/ipython/IPython/html/static/*
>> *make: r.js: No se encontró el programa*
>> *make: *** [static/require/build/widgets.js] Error 127*
>>
>> It seems it is a missing file.
>>
>>>
>>>
> I can confirm this (or a very similar) problem while installing the spkg. 
>  It occurs some time after the backports error.
>
> gcc -o submodules/jsmin-bin submodules/jsmin/jsmin.c
> r.js -o static/require/main.js 
> appDir=/Users.../sage/local/lib/python2.7/site-packages/IPython/html/static/
> make: r.js: No such file or directory
> make: *** [static/require/build/widgets.js] Error 1
> Error minifying javascript and CSS.
>
>
One solution appears to be to get npm and then 
npm install -g inherits requirejs coffee-script ##installs r.js 
==required.js
(see https://github.com/sagemath/sagecell/blob/master/doc/installation.rst)
but I would hope there is an easier way than that long-term, since that set 
of instructions seems very redundant in some ways to the spkg way of 
installing it.

It appears that the current maintainer is working on updating the 
installation instructions, so hopefully within a week or so that will be 
much clearer :)

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Cygwin: Error installing package mpir-2.6.0.p4

[Chris Doris]

Thanks for your reply, Jean-Pierre.

I installed Cygwin from the x86_64 setup executable. Is this what you're
calling Cygwin64?

Do I take it that the Cygwin entry on the supported platforms wiki page is
only referring to the 32 bit version of Cygwin? Should someone add an entry
for Cygwin64? Can/should I do that?

What are the options for me? It looks like building Sage on Cygwin64 will
take a lot of effort (or is impossible). I'd rather not have to dual-boot
my computer into Linux to use Sage, and I'm not sure how well
virtualization will work (it's a fairly low powered laptop) but I'll give
that a go. Will Cygwin32 work?

Thanks,
Christopher
On 8 Jul 2014 09:52, "Jean-Pierre Flori"  wrote:

> Please have a look at http://trac.sagemath.org/sage_trac/wiki/Cygwin64Port
> which contains the latest info.
>
> Did you install Cygwin32 or Cygwin64?
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/30vaC74-5cI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Problem installing sagecell

[kcrisman]

>
> I'm trying with the new package but I still obtain error. I have tried 
> your solution but:
>
> *sagecell@kimba:~/sage/sagecell$ ../sage -sh -c "make -B"*
> *if git submodule status | grep -q ^[+-]; then git submodule update --init 
> > /dev/null; fi*
> *python -c "import urllib; 
> urllib.urlretrieve('http://code.jquery.com/jquery-2.1.0.min.js 
> ', 'static/jquery.min.js')"*
> *gcc -o submodules/jsmin-bin submodules/jsmin/jsmin.c*
> *r.js -o static/require/main.js 
> appDir=/home/sagecell/sage/ipython/IPython/html/static/*
> *make: r.js: No se encontró el programa*
> *make: *** [static/require/build/widgets.js] Error 127*
>
> It seems it is a missing file.
>
>>
>>
I can confirm this (or a very similar) problem while installing the spkg. 
 It occurs some time after the backports error.

gcc -o submodules/jsmin-bin submodules/jsmin/jsmin.c
r.js -o static/require/main.js 
appDir=/Users.../sage/local/lib/python2.7/site-packages/IPython/html/static/
make: r.js: No such file or directory
make: *** [static/require/build/widgets.js] Error 1
Error minifying javascript and CSS.

 

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Problem installing sagecell

[kcrisman]

>
> After installing ipython-2.0.0.tar.gz, got this error message:
>
>
Hopefully you wouldn't need to do this; Sage now has an up-to-date (enough) 
Ipython on its own. 

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Do ticket titles matter? Can I rename a ticket if I didn't open it?

[kcrisman]

Needless to say, the code stays the same. And of course I still prefer my 
> original title, which was funnier and more human. But well, nice and 
> respectful conversations lead to better compromises :-P
>
>
+1

Thanks, Robert, for clarifying things well - and with no spelling errors :) 

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Where is the long_element (or w0) method of Coxeter groups gone?

[jplab]

Hi,

I had some older code using Coxeter groups. Since I was running the code on 
machines with different version of Sage, I was handling manually if whether 
it had "CoxeterGroup" or not (I used WeylGroup when needed). 

Now I'm rebasing my code to the latest version of Sage, and to my surprise, 
there seems not to have a method to get the longest element anymore?

For WeylGroup, I can get .longest_element_hardcoded(). Nevertheless, I do 
not want to work with WeylGroups since I also need several things about 
Coxeter groups.

What happened to the method formerly known as .w0?

Thank you,
Jean-Philippe

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: (eventual) patchbot replacement

[Volker Braun]

Sounds good to me! 

For tarballs and their testing we should have some automated way to upload 
them. Me ssh'ing into the web server and manually downloading it to the 
right directory isn't a good workflow. That would also solve your problem 
for testing.


On Tuesday, July 8, 2014 2:27:05 AM UTC-4, R. Andrew Ohana wrote:
>
> bump.
>
> In case anyone has actual feedback. I will try to roll out these changes 
> sometime next week.
>

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: strange (to me) doctest failure

[Martin Albrecht]

Sure, this was about fixing a bug introduced in said ticket (which I now found 
:)

On Tuesday 08 Jul 2014 00:29:18 Eric Gourgoulhon wrote:
> Hi,
> 
> Le lundi 7 juillet 2014 22:22:10 UTC+2, Martin Albrecht a écrit :
> > Hi,
> > 
> > over at http://trac.sagemath.org/ticket/12718 I am encountering a strange
> > doctest failure:
> > 
> > This will fail in a fresh instance of Sage:
> > sage: matrix(QQ['x,y'], 2, 2, [1, 1, 1, 1]) / x
> > 
> > with a TypeError (no error message)
> 
>  It works for me (with Sage 6.2):
> 
> 
┌┐
> │ Sage Version 6.2, Release Date: 2014-05-06 │
> │ Type "notebook()" for the browser-based notebook interface.│
> │ Type "help()" for help.│
> 
└┘
> sage: matrix(QQ['x,y'], 2, 2, [1, 1, 1, 1]) / x
> [1/x 1/x]
> [1/x 1/x]
> 
> Best wishes,
> 
> Eric.

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Cygwin: Error installing package mpir-2.6.0.p4

[Jean-Pierre Flori]

Please have a look at http://trac.sagemath.org/sage_trac/wiki/Cygwin64Port 
which contains the latest info.

Did you install Cygwin32 or Cygwin64?

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: strange (to me) doctest failure

[Eric Gourgoulhon]

Hi,

Le lundi 7 juillet 2014 22:22:10 UTC+2, Martin Albrecht a écrit :
>
> Hi, 
>
> over at http://trac.sagemath.org/ticket/12718 I am encountering a strange 
> doctest failure: 
>
> This will fail in a fresh instance of Sage: 
>
> sage: matrix(QQ['x,y'], 2, 2, [1, 1, 1, 1]) / x 
>
> with a TypeError (no error message) 
>


 It works for me (with Sage 6.2):

┌┐
│ Sage Version 6.2, Release Date: 2014-05-06 │
│ Type "notebook()" for the browser-based notebook interface.│
│ Type "help()" for help.│
└┘
sage: matrix(QQ['x,y'], 2, 2, [1, 1, 1, 1]) / x
[1/x 1/x]
[1/x 1/x]

Best wishes,

Eric.

-- 
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.