Re: [sage-combinat-devel] SetPartitions inconsistency when treating strings

2010-01-28 Thread Florent Hivert 
   Hi there,

[...]
> SetPartitions('aabcd', [3,2]).cardinality()
> ///
> Traceback (most recent call last):
[...]
> SetPartitions('aabcd').list()
> ///
> Traceback (most recent call last):
[...]

Thanks Harald for reporting that. I took care of tracking down the bug. It can
be "solved" by just removing a "Set" !!! However, I have a design question:
I don't know how to return a sensible results:
According to the doc:
 sage: s = SetPartitions('aa')
Models the set-partition of a *two* element set {a1, a2} where the two a are
different. So that,
 sage: s.cardinality()
 2
And 
 sage: s.list()
Should return
 [{{'a1', 'a2'}}, {{'a1'}, {'a2'}}]
However since the two 'a' are by no means different, I've no way to prevent
sage to simplify {{'a', 'a'}} in {{'a'}} and {{'a'}, {'a'}} in {{'a'}}

I see two solutions:

  1) change the interface and forbid the input of string with repeated letters

  2) add an option to returns the partitions as list of list. The user must
turn this option on if he wants a sensible result in the case of repeated
letters.

So my question is: are there any use case for option 2 ?

Any other suggestions ? 

Cheers,

Florent

-- 
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-de...@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] ** unknown exception encountered, details follow

2010-01-28 Thread Nicolas M. Thiery 
On Thu, Jan 28, 2010 at 04:52:55PM +0100, Sébastien Labbé wrote:
> I am currently having a strange problem with the sage-combinat tree.
> Are you experiencing a similar thing?

Oops, I am probably the culprit. I had this problem quite a few
time. Somehow from time to time in my workflow, a strange character is
inserted at the top of the series file which confuses hg. I haven't
found yet a systematic way to reproduce it. Clue anyone?

In the mean time: fixed and pushed.

Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" 
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-de...@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] ** unknown exception encountered, details follow

2010-01-28 Thread Sébastien Labbé 
Bonjour sage-combinat,

I am currently having a strange problem with the sage-combinat tree.
Are you experiencing a similar thing?

Sébastien

sla...@pol:~/sage-4.3.1/devel/sage-combinat$ hg qpop -a
aucun patch appliqué
sla...@pol:~/sage-4.3.1/devel/sage-combinat$ hg qpush
application de 
impossible de lire 
** unknown exception encountered, details follow
** report bug details to http://mercurial.selenic.com/bts/
** or mercur...@selenic.com
** Mercurial Distributed SCM (version 1.3.1)
** Extensions loaded: mq, extdiff
Traceback (most recent call last):
  File "/home/slabbe/sage-4.3.1/local/bin/hg", line 27, in 
mercurial.dispatch.run()
  File "/home/slabbe/sage-4.3.1/local/lib/python/mercurial/dispatch.py",
line 16, in run
sys.exit(dispatch(sys.argv[1:]))
  File "/home/slabbe/sage-4.3.1/local/lib/python/mercurial/dispatch.py",
line 27, in dispatch
return _runcatch(u, args)
  File "/home/slabbe/sage-4.3.1/local/lib/python/mercurial/dispatch.py",
line 43, in _runcatch
return _dispatch(ui, args)
  File "/home/slabbe/sage-4.3.1/local/lib/python/mercurial/dispatch.py",
line 449, in _dispatch
return runcommand(lui, repo, cmd, fullargs, ui, options, d)
  File "/home/slabbe/sage-4.3.1/local/lib/python/mercurial/dispatch.py",
line 317, in runcommand
ret = _runcommand(ui, options, cmd, d)
  File "/home/slabbe/sage-4.3.1/local/lib/python/mercurial/dispatch.py",
line 501, in _runcommand
return checkargs()
  File "/home/slabbe/sage-4.3.1/local/lib/python/mercurial/dispatch.py",
line 454, in checkargs
return cmdfunc()
  File "/home/slabbe/sage-4.3.1/local/lib/python/mercurial/dispatch.py",
line 448, in 
d = lambda: util.checksignature(func)(ui, *args, **cmdoptions)
  File "/home/slabbe/sage-4.3.1/local/lib/python/mercurial/util.py",
line 402, in check
return func(*args, **kwargs)
  File "/home/slabbe/sage-4.3.1/local/lib/python/hgext/mq.py", line
2117, in push
mergeq=mergeq, all=opts.get('all'))
  File "/home/slabbe/sage-4.3.1/local/lib/python/hgext/mq.py", line 979, in push
top = self.applied[-1].name
IndexError: list index out of range

-- 
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-de...@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.