Hi Francois,
On 2015-01-06, Francois Bissey francois.bis...@canterbury.ac.nz wrote:
Are you meaning that you still update it as an “old” spkg?
Yes. Reason? Hm. The best reason I have is this: The code in the spkg
has never been published elsewhere, and thus I think that the spkg *is*
upstream.
Hi,
it could be nice to have a list of the non-migrated spkgs that are still
needed. Depending on its size, working on a raw migration to get rid of
the old-style spkgs will be a great simplification.
As for me, i see:
- cbc
- nauty
A side effect would be to easily fix the currently broken
I mean “spkg”. Automated spellchecker can be a pain, I clearly remember now why
I had
disabled it on my iPad.
On 6/01/2015, at 21:24, Francois Bissey francois.bis...@canterbury.ac.nz
wrote:
spoke
--
You received this message because you are subscribed to the Google Groups
sage-devel
Are you meaning that you still update it as an “old” spkg?
Seriously I thought Nathann was only talking about producing such a spkg.
And that I really think we can drop. If someone care about making new
old style spoke, they can use an old sage for that.
François
On 6/01/2015, at 20:33, Simon
http://justinhileman.info/article/git-pretty/
--
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
Again it depends on the case. Not every algorithm needs to be documented,
some things are necessarily assumed to be known to anybody who wants to
make relevant changes. I don't think Sage explains the algorithm for
solving CRT anywhere...
Agree. I did not have in mind well-known
Hello !
Despite from that I hope you understand what I have in mind with developer
documentation.
I totally agree with you on this respect. The documentation that Jori
wanted to write totally fits with your example: there is a class that
we did not write ourselves and that we do not understand
Well, that's two people already...
Yepyep.
For the time being perhaps one can change the wording to indicate only for
legacy packages, we expect new packages to be in this format.
I have to say that needing a patch for ''every'' upgrade of a pkg is
annoying, sage -i should just work.
Last August, I released the first version of my slabbe-0.1.spkg. I had to
choose at that time between the old-style and the new style. I explained
here [1] why I finally choose the old-style. If I use the new style and I
release slabbe-0.2 tomorrow during a conference let say for fixing a bug
See http://trac.sagemath.org/ticket/4970 - I have a feeling this is long
since superseded
I agree: Tkinter works out-of-the box on OS X with any recent source or
binary release of Sage.
Can you review that ticket, then? I have no experience with Tkinter
myself.
--
You received
Last August, I released the first version of my slabbe-0.1.spkg. I had to
choose at that time between the old-style and the new style. I explained
here [1] why I finally choose the old-style. If I use the new style and I
release slabbe-0.2 tomorrow during a conference let say for fixing a
On Tuesday, January 6, 2015 3:51:29 PM UTC+1, John Cremona wrote:
By the way, there is discussion of building Pari under Cygwin 64 on
the pari-dev list; bugs are being discovered and fixed as I type.
Great news!
My last findings were that PARI behaved very badly on Cygwin64.
For example
By the way, there is discussion of building Pari under Cygwin 64 on
the pari-dev list; bugs are being discovered and fixed as I type.
John
On 27 November 2014 at 17:39, Jean-Pierre Flori jpfl...@gmail.com wrote:
And I forgot http://trac.sagemath.org/ticket/17365 and
Hi Karl-Dieter,
On 2015-01-06, kcrisman kcris...@gmail.com wrote:
I have to say that needing a patch for ''every'' upgrade of a pkg is
annoying, sage -i should just work.
Every upgrade should be reviewed. So, it must not be possible that a
change in the upstream sources is automatically
Hi,
Who is also going to the Joint Mathematics Meetings in San Antonio?
-- William
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this
On Sat, Jan 3, 2015 at 8:23 PM, William Stein wst...@gmail.com wrote:
Hi,
The computer combinat.math.washington.edu is down... again. Sort of.
It responds to ping requests, but I can't ssh in.
A minor update: there are notifications about physical hardware
failures on the front of the
I have to say that needing a patch for ''every'' upgrade of a pkg is
annoying, sage -i should just work.
Every upgrade should be reviewed. So, it must not be possible that a
Sorry, I meant that to upgrade an spkg the end user shouldn't have to do
anything.
change in the
http://justinhileman.info/article/git-pretty/
the presentation isn't bad, either.
Don't bite off more than I can chew. If you send me an epic pull request,
I'm likely to stare blankly at it for a second, then move on to a shorter
one.
I think this is a problem of a lot of our tickets.
I agree: Tkinter works out-of-the box on OS X with any recent source or
binary release of Sage.
Can you review that ticket, then? I have no experience with Tkinter
myself.
Sure, but what does that mean given that nothing needs to be done? More
specifically, what trac status should
On Tuesday, January 6, 2015 4:02:45 PM UTC+1, Jean-Pierre Flori wrote:
On Tuesday, January 6, 2015 3:51:29 PM UTC+1, John Cremona wrote:
By the way, there is discussion of building Pari under Cygwin 64 on
the pari-dev list; bugs are being discovered and fixed as I type.
Great news!
20 matches
Mail list logo
