[sage-combinat-devel] Re: problems with some files in the queue

2012-07-13 Thread Travis Scrimshaw
11305 patch changed.

Best,
Travis


On Thursday, July 12, 2012 11:14:19 PM UTC+1, John H Palmieri wrote:

 In the combinat queue, some files contain non-ascii characters. Several 
 participants at Sage-Combinat Days 40 have run into problems with this: 
 when there are non-ascii characters, if you clone the combinat queue, you 
 get errors when building Sage and its documentation.

 - trac_11305-rigged_configurations-ts.patch: line 1064 (in 187–201) 
 contains a character which looks like a hyphen, but is not, so it needs to 
 be replaced.

 - trac_11929_8899-ncsf-qsym-fs.patch: line 77 has a similar problem 
 (218–348).

 - separatrix_diagram-vd.patch: line 2179 looks something like this:

 +`vef = 1` and the action of the group generated by `v,e,f` acts 
 transitvely

 but there are two characters of gibberish before `v,e,f`. They should be 
 deleted.

 - trac_12518-enumerated_set_from_iterator-vd.patch: line 476 has a 
 character (immediately after the #) which looks like a space but isn't. 
 Maybe Franco has fixed this already, but please check.

 -- 
 John



-- 
You received this message because you are subscribed to the Google Groups 
sage-combinat-devel group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/sage-combinat-devel/-/wmvPLCSllEYJ.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.



[sage-combinat-devel] Re: queue broken

2012-07-13 Thread Travis Scrimshaw
Hey,
   I'm also getting an error when 
applying trac_9265_tableaux_categories_jb.patch. Is this related?

Best,
Travis


On Thursday, July 12, 2012 7:46:15 PM UTC+1, Anne Schilling wrote:

 Hi! 

 The patch queue is currently broken with sage-5.1. 
 Nicolas claims that he fixed this before lunch, so Chris, 
 did you make changes since that break the queue? 

 Thanks, 

 Anne 


-- 
You received this message because you are subscribed to the Google Groups 
sage-combinat-devel group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/sage-combinat-devel/-/9yN-IChX0mYJ.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.



Re: [sage-combinat-devel] Root systems do not define variables correctly

2012-07-13 Thread VulK
Hi,
I guess injecting simple roots would be my choice.
If not possible, at least, it would be cleaner to remove inject_variables
from the auto completion list for A.
S.

* Nicolas M. Thiery nicolas.thi...@u-psud.fr [2012-07-12 23:47:34]:

 On Thu, Jul 12, 2012 at 11:08:54PM -0400, VulK wrote:
  I just noticed the following odd behaviour:
  
   sage: L=RootSystem(['A',2]).root_lattice()
   sage: L.inject_variables()
   ---
   ValueErrorTraceback (most recent call 
   last)
   ValueError: variable names have not yet been set using
  
  I am running Sage Version 5.1, Release Date: 2012-07-09 with combinat queue
  both compiled from sources today (I noticed the same behaviour on an old 4.8
  install and I upgraded to check if had already been addressed).
  I assume it will suffices to add _assign_names in the definition of
  root_lattice but I did not have time to check it.
 
 What would you want this method to do for root lattices?
 
   Nicolas
 --
 Nicolas M. Thiéry Isil nthi...@users.sf.net
 http://Nicolas.Thiery.name/
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 sage-combinat-devel group.
 To post to this group, send email to sage-combinat-devel@googlegroups.com.
 To unsubscribe from this group, send email to 
 sage-combinat-devel+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/sage-combinat-devel?hl=en.
 

-- 
You received this message because you are subscribed to the Google Groups 
sage-combinat-devel group.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.



Re: [sage-combinat-devel] Re: queue broken

2012-07-13 Thread Anne Schilling
Hi Travis,

For me everything applies fine under sage-5.1. Which version of sage are you 
using?
You should upgrade to sage-5.1 most likely!

Anne

On 7/13/12 4:23 AM, Travis Scrimshaw wrote:
 Hey,
I'm also getting an error when applying 
 trac_9265_tableaux_categories_jb.patch. Is this related?
 
 Best,
 Travis
 
 
 On Thursday, July 12, 2012 7:46:15 PM UTC+1, Anne Schilling wrote:
 
 Hi!
 
 The patch queue is currently broken with sage-5.1.
 Nicolas claims that he fixed this before lunch, so Chris,
 did you make changes since that break the queue?
 
 Thanks,
 
 Anne
 

-- 
You received this message because you are subscribed to the Google Groups 
sage-combinat-devel group.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.



[sage-combinat-devel] Re: queue broken

2012-07-13 Thread Hugh Thomas

The queue is applying to 5.0 fine for me.  -Hugh

On Thursday, July 12, 2012 9:46:15 PM UTC+3, Anne Schilling wrote:

 Hi! 

 The patch queue is currently broken with sage-5.1. 
 Nicolas claims that he fixed this before lunch, so Chris, 
 did you make changes since that break the queue? 

 Thanks, 

 Anne 


-- 
You received this message because you are subscribed to the Google Groups 
sage-combinat-devel group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/sage-combinat-devel/-/ZBgzO-vXl4AJ.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.



Re: [sage-combinat-devel] Root systems do not define variables correctly

2012-07-13 Thread Nicolas M. Thiery
On Fri, Jul 13, 2012 at 08:07:48AM -0400, VulK wrote:
 I guess injecting simple roots would be my choice.

That could make sense since they are the generators. However I am not
sure what name to give them (they are indexed by 1,2,3). In this case,
I guess I'd rather implement inject_shorthands that would inject
respectively s, alpha, alphacheck, ... for
L.simple_reflections(), L.simple_roots(), L.simple_coroots(), ...

 If not possible, at least, it would be cleaner to remove
 inject_variables from the auto completion list for A.

I agree: this method should ideally be lower in the class hierarchy
(it's in CategoryObject right now). If you find a lower class that
covers all current proper use cases, please create a ticket. I guess
Parent would be a good start even though it would not change anything
for root lattices. Otherwise, there could be a comment in the
documentation of CategoryObject.inject_shorthands stating that this
only works for parents whose generators have names that can be mapped
to Python identifiers. Feel free to proceed on that, after checking
whether there has been any discussion on sage-devel/trac recently
about inject_variables.

Cheers,
Nicolas
--
Nicolas M. Thiéry Isil nthi...@users.sf.net
http://Nicolas.Thiery.name/

-- 
You received this message because you are subscribed to the Google Groups 
sage-combinat-devel group.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.



Re: [sage-combinat-devel] Re: queue broken

2012-07-13 Thread Mike Zabrocki
Hi,
We are in the last few hours of sage days and I had to disable a few 
patches.
I didn't figure what the cause was in these cases, only that they weren't 
working
for me now.
We made changes on symmetric functions so I am sure that Martin's
patch is failing to apply at least partly because of that.

sf_principal_specialization-mr.patch
trac_6538-partitions_max_slope-ts.patch 

I don't know what is failing with Travis' patch.
I'll try to restore them later.

-Mike


On Friday, 13 July 2012 09:14:47 UTC-5, Anne Schilling wrote:

 Hi Travis, 

 For me everything applies fine under sage-5.1. Which version of sage are 
 you using? 
 You should upgrade to sage-5.1 most likely! 

 Anne 

 On 7/13/12 4:23 AM, Travis Scrimshaw wrote: 
  Hey, 
 I'm also getting an error when applying 
 trac_9265_tableaux_categories_jb.patch. Is this related? 
  
  Best, 
  Travis 
  
  
  On Thursday, July 12, 2012 7:46:15 PM UTC+1, Anne Schilling wrote: 
  
  Hi! 
  
  The patch queue is currently broken with sage-5.1. 
  Nicolas claims that he fixed this before lunch, so Chris, 
  did you make changes since that break the queue? 
  
  Thanks, 
  
  Anne 
  


-- 
You received this message because you are subscribed to the Google Groups 
sage-combinat-devel group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/sage-combinat-devel/-/Qiv01TbSDOQJ.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.