Thanks Anne. Yes, I did a clean install of sage-combinat, but I think I
forgot to to a hg init, which might have caused my problem??
I am sure that I am not in the default tip. The question, how do I get
into it?
When I do a commit should I merge using revision number from my patch or
some
Hi Andrew--
I think the problem is that there is no problem! When you updated after
making your changes, mercurial updated your repository by merging your
version with the most current version on the server. Then when you pushed,
the server was updated to that updated version as well. (The
Hi Andrew,
If you did reinstall your sage-combinat, then there should not be any problem.
Looking at your last commit, it looked to have gone through fine!
The usual workflow is as follows:
- update from the queue frequently since there is a lot of flow and you want to
have the most up to
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
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.
-
Hi,
I just noticed the following odd behaviour:
sage: L=RootSystem(['A',2]).root_lattice()
sage: L.inject_variables()
---
ValueErrorTraceback (most recent call last)
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()
---
ValueError
