Re: [sage-devel] modulo is broken in some (fairly simple) rings
Anyway, this is now : http://trac.sagemath.org/ticket/16276 waiting for a ---very simple--- review. (All test pass for me) --- Charles On 30 Apr 2014, at 11:36, John Cremona wrote: > On 30 April 2014 10:13, Jean-Pierre Flori wrote: >> >> >> On Wednesday, April 30, 2014 11:04:06 AM UTC+2, John Cremona wrote: >>> >>> On 30 April 2014 09:35, Jean-Pierre Flori wrote: On Wednesday, April 30, 2014 8:28:24 AM UTC+2, Charles Bouillaguet wrote: > > Hi all, > > I just noticed that we carefully check that Sage computes something > completely wrong. From sage/structure/element.pyx, line 2052 : > > -- > When little is implemented about a given ring, then mod may >return simply return `f`. For example, reduction is not >implemented for `\ZZ[x]` yet. (TODO!) > >sage: R. = PolynomialRing(ZZ) >sage: f = x^3 + x + 1 >sage: f.mod(x + 1) >x^3 + x + 1 > -- > > The problem is that mod() does the following : > > from sage.rings.ideal import is_Ideal >if not is_Ideal(I) or not I.ring() is self._parent: >I = self._parent.ideal(I) >#raise TypeError, "I = %s must be an ideal in %s"%(I, > self.parent()) >return I.reduce(self) > > So, mod relies on Ideal.reduce, which by default does nothing and > returns > its argument. As such, mod is badly broken. > > What seems reasonable is to make Ideal.reduce() raise a > NotImplementedError by default instead of doing nothing, by this breaks > a > lot of other stuff (because Ideal.reduce() is called a lot). > > What do you think is right ? > > *) Go with NotImplementedError and fix 30+ doctests? > *) create a StopGap that warn the user that mod may be complete > rubbish? > > Cheers, > --- > Charles Bouillaguet > http://www.lifl.fr/~bouillaguet/ > Wouldn't modify the mod method for polynomial rings over ZZ be enough? In a similar way, the pow (python?) function accepts an optional "modulus" third args, but Sage just ignores it over a bunch of rings. For example, over QQ, pow(x,100,x+1) yields x^100. For non euclidean rings that might be a sensible default choice but for euclidean rings or even just univariate polynomial rings over fields we might want to modify that (maybe something for the category framework as Luca De Feo suggested). >>> >>> Of course ZZ[X] is not Euclidean and it is not clear (to me) what a >>> good definition of reduction modulo (say) 2*X+1 should be. But >>> reduction modulo a monic polynomial is easy, and that special case >>> would be worth having even if one did nothing in the general case. >>> >>> Quiz question: what do YOU think that the reduction of X^100 modulo >>> 2X+1 should be? >>> >> Good question... >> We had a look around last week to gather info about what other libs do and >> IIRC, at least for flint, what happens is that start at top degree monomial >> you substract the largest multiple of the modulus so that the leading >> coefficient is positive (did not look at negative leading coeffs...). >> In fact, that's also what Sage does when you do (x^100) % (x^2+1) (which >> does not call the same function as pow(x,100,x^2+1)). >> >> Anyway in my case, where I wanted fast modular exponentiation, so reducing >> at each step was necessary to keep degrees low, such a case does not make >> sense as with such a definition the resulting polynomial has high degree >> anyway (and I don't really care about such a case...). > > Sure. I think the underlying mathematical issue is that Z[X]/(2*X+1) > is not finitely-generated as an abelian group, (equivalently, -1/2 is > not an algebraic integer), so it is hopless to look for a finite set > of "residues" with the property that everything reduces to a Z-linear > combination of these. As a ring this is Z[1/2] so one choice is to > return the rational number obtained by substituting -1/2 for X. But I > think that if Sage were to return 2^-50 for X^100 % (2*X+1) we would > get complaints > > Sorry for the overkill, I have just been teaching a course in > commutative algebra! > > John > >> >> -- >> 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. > > -- > 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
Re: [sage-devel] Re: R graphics and pkg-config (trac #15742)
On Fri, 02 May 2014 01:34:42 leif wrote:
> François Bissey wrote:
> > On Thu, 01 May 2014 15:05:03 Volker Braun wrote:
> >> On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote:
> pkg-config --variable pc_path pkg-config
> >>>
> >>> That doesn't always work. (See my other post on how to get it.)
> >>
> >> Where does it not work?
> >
> > My SLES11SP1 system on power7 reports:
> > frb15@p2n14-c /hpc/home/frb15 :/usr/bin/pkg-config --variable pc_path pkg-
> > config
> >
> > frb15@p2n14-c /hpc/home/frb15 :/usr/bin/pkg-config --version
> > 0.23
> >
> > It just report blank for that particular command but I checked it
> > reports configuration of system libraries OK so it is not broken.
>
> Same for 0.22 here on Ubuntu 10.04.4.
>
> 0.25 does support it. (Also supports ... --debug 2>&1 | grep
> '^Scanning' ...)
>
> And:
>
> $ pkg-config --variable pc_path pkg-config
> $ pkg-config --debug 2>&1 | grep '^Scanning' | awk '{print $3}'
> '/usr/lib/pkgconfig'
> $ pkg-config --version
> 0.15.0
> $ uname -rs
> SunOS 5.10
>
For some reason I found our AIX system defaulted on an antique 0.14
version that someone installed before my time.
frb15@p1n14-c /hpc/home/frb15 :pkg-config --version
0.14.0
frb15@p1n14-c /hpc/home/frb15 :pkg-config --variable pc_path pkg-config
frb15@p1n14-c /hpc/home/frb15 :pkg-config --debug 2>&1 | awk '/^Scanning
/{print substr($3,2,length($3)-2)}'
/usr/local/lib/pkgconfig
But it was hiding 0.19 on the system so I don't quite officially beat you
for the oldest version around :)
frb15@p1n14-c /hpc/home/frb15 :uname -rsv
AIX 1 6
And it should be read AIX 6.1. True IBM fashion.
Francois
--
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: R graphics and pkg-config (trac #15742)
François Bissey wrote:
On Thu, 01 May 2014 15:05:03 Volker Braun wrote:
On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote:
pkg-config --variable pc_path pkg-config
That doesn't always work. (See my other post on how to get it.)
Where does it not work?
My SLES11SP1 system on power7 reports:
frb15@p2n14-c /hpc/home/frb15 :/usr/bin/pkg-config --variable pc_path pkg-
config
frb15@p2n14-c /hpc/home/frb15 :/usr/bin/pkg-config --version
0.23
It just report blank for that particular command but I checked it
reports configuration of system libraries OK so it is not broken.
Same for 0.22 here on Ubuntu 10.04.4.
0.25 does support it. (Also supports ... --debug 2>&1 | grep
'^Scanning' ...)
And:
$ pkg-config --variable pc_path pkg-config
$ pkg-config --debug 2>&1 | grep '^Scanning' | awk '{print $3}'
'/usr/lib/pkgconfig'
$ pkg-config --version
0.15.0
$ uname -rs
SunOS 5.10
:-)
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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: git diff branch1..develop
Dear list,
On Thu, 1 May 2014 22:21:51 + (UTC)
Simon King wrote:
> On 2014-05-01, Dima Pasechnik wrote:
> > did you look at
> > http://boxen.math.washington.edu/home/vbraun/doc/developer/git_trac.html#section-git-trac-readonly
> > ?
>
> Yes. I understand that it tells me how to configure stuff so that I can
> *only* pull (and this without password), but can not push (even with
> password).
I don't see why I would be impossible to use read-only for fetching and
ssh-key for pushing. In fact, with git >= 1.6.4 (needed according to
[1]) and with this in my .git/config:
[remote "trac"]
pushurl = g...@trac.sagemath.org:sage.git
url = git://trac.sagemath.org/sage.git
fetch = +refs/heads/*:refs/remotes/trac/*
which yields this from "git remote -v":
origin git://github.com/sagemath/sage.git (fetch)
origin git://github.com/sagemath/sage.git (push)
tracgit://trac.sagemath.org/sage.git (fetch)
tracg...@trac.sagemath.org:sage.git (push)
I can push to trac with my ssh-key-password (the branch I pushed is at
[2]) and fetch from trac without a password. It's a bit too late in the
evening for me to learn git-trac now, so I tried this only with pure
git ("git fetch trac" and "git push trac master:u/emassop/test"). I
really don't see why this would interfere with git-trac though.
Regards,
Erik Massop
[1]
http://technosorcery.net/blog/2011/12/26/how-i-use-different-fetch-and-push-urls-in-git/
[2] http://git.sagemath.org/sage.git/log/?h=u/emassop/test
--
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: R graphics and pkg-config (trac #15742)
On Fri, 02 May 2014 11:04:35 François Bissey wrote:
> On Thu, 01 May 2014 15:05:03 Volker Braun wrote:
> > On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote:
> > > > pkg-config --variable pc_path pkg-config
> > >
> > > That doesn't always work. (See my other post on how to get it.)
> >
> > Where does it not work?
>
> My SLES11SP1 system on power7 reports:
> frb15@p2n14-c /hpc/home/frb15 :/usr/bin/pkg-config --variable pc_path pkg-
> config
>
> frb15@p2n14-c /hpc/home/frb15 :/usr/bin/pkg-config --version
> 0.23
>
> It just report blank for that particular command but I checked it
> reports configuration of system libraries OK so it is not broken.
>
Oh and Leif's idea reports:
frb15@p2n14-c /hpc/home/frb15 :pkg-config --debug 2>&1 | awk '/^Scanning
/{print substr($3,2,length($3)-2)}'
/usr/local/lib/pkgconfig
/usr/lib64/pkgconfig
/usr/share/pkgconfig
If I don't parse the output I can see that it actually tried to also
open /usr/local/lib64/pkgconfig and /usr/local/share/pkgconfig but these
folders don't exist so they weren't "scanned".
Francois
--
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: R graphics and pkg-config (trac #15742)
On Thu, 01 May 2014 15:05:03 Volker Braun wrote: > On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote: > > > pkg-config --variable pc_path pkg-config > > > > That doesn't always work. (See my other post on how to get it.) > > Where does it not work? My SLES11SP1 system on power7 reports: frb15@p2n14-c /hpc/home/frb15 :/usr/bin/pkg-config --variable pc_path pkg- config frb15@p2n14-c /hpc/home/frb15 :/usr/bin/pkg-config --version 0.23 It just report blank for that particular command but I checked it reports configuration of system libraries OK so it is not broken. Francois -- 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: R graphics and pkg-config (trac #15742)
On Thu, May 01, 2014 at 10:58:47PM +0200, leif wrote: > Felix Salfelder wrote: > >pkg-config --variable pc_path pkg-config > > That doesn't always work. (See my other post on how to get it.) if so (when?), how about fallback to something more complex *in case it does not*? reportedly, --debug does not always exist either. cheers felix -- 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: git diff branch1..develop
> > salted, I presume. > Trac relies on plaintext (well http digest) authentication, so we need the plaintext password. As always, use different passwords for each account ;-) -- 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: git diff branch1..develop
On 2014-05-01, leif wrote: > Dima Pasechnik wrote: >>> Why am I asked for my trac password when I just pull? Shouldn't a >>> password only be required for pushing, but not for pulling? >> >> did you look at >> http://boxen.math.washington.edu/home/vbraun/doc/developer/git_trac.html#section-git-trac-readonly >> ? >> >> It also seems that you'd only need to do >> git trac config --user USERNAME --pass 'PASSWORD' >> once, and it will store the data somewhere... > > Somewhere...?! salted, I presume. Or do you mean to say that you never ever trust your computer so store your password? Not even in /etc/passwd ? Then you probably work in MSDOS... :-) > > I wouldn't recommend anyone to use that feature; it's IMHO odd it's even > there. > > > -leif > > -- > () The ASCII Ribbon Campaign > /\ Help Cure HTML E-Mail > -- 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: git diff branch1..develop
Hi Dima, On 2014-05-01, Dima Pasechnik wrote: > did you look at > http://boxen.math.washington.edu/home/vbraun/doc/developer/git_trac.html#section-git-trac-readonly > ? Yes. I understand that it tells me how to configure stuff so that I can *only* pull (and this without password), but can not push (even with password). Best regards, Simon -- 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: git diff branch1..develop
On Thursday, May 1, 2014 11:16:38 PM UTC+1, leif wrote: > > Somewhere...?! > In .git/config, of course. Basically an alias for git config --local trac.username=... -- 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: git diff branch1..develop
Dima Pasechnik wrote: Why am I asked for my trac password when I just pull? Shouldn't a password only be required for pushing, but not for pulling? did you look at http://boxen.math.washington.edu/home/vbraun/doc/developer/git_trac.html#section-git-trac-readonly ? It also seems that you'd only need to do git trac config --user USERNAME --pass 'PASSWORD' once, and it will store the data somewhere... Somewhere...?! I wouldn't recommend anyone to use that feature; it's IMHO odd it's even there. -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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: git diff branch1..develop
On Thursday, May 1, 2014 10:01:36 PM UTC+1, Simon King wrote: > > I immediately started playing with it, and I wonder: Can I configure > it so that "git trac review 12345" shows me the diff in "less" (or another > pager)? git does use "less" when I call "git log" or "git diff ...", but > I don't see any hint in ~/.gitconfig why less is used on the log and the > diff but not on "trac review". > The script does some merging in a detached head and then switches back to your branch before printing the diff. If we want to let git display the pager then the repo would have to stay in the detached head until we close the pager. Not necessarily a problem, but I thought its safer to switch back as soon as possible. You can always do "git trac review | less -R" -- 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: git diff branch1..develop
Trac password or ssh password for the git authentication? You shouldn't need a trac password (though I probably don't test that), but you need a ssh key unless you follow the "Readonly repository" instructions. On Thursday, May 1, 2014 10:49:22 PM UTC+1, Simon King wrote: > > Hi! > > Next question: > > On 2014-05-01, Simon King > wrote: > > I immediately started playing with it, and I wonder: Can I configure > > it so that "git trac review 12345" shows me the diff in "less" (or > another > > pager)? git does use "less" when I call "git log" or "git diff ...", but > > I don't see any hint in ~/.gitconfig why less is used on the log and the > > diff but not on "trac review". > > Why am I asked for my trac password when I just pull? Shouldn't a > password only be required for pushing, but not for pulling? > > Best regards, > Simon > > > -- 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: R graphics and pkg-config (trac #15742)
On Thursday, May 1, 2014 9:25:52 PM UTC+1, leif wrote:
>
> $ pkg-config --debug 2>&1 | awk '/^Scanning /{print
Pkgconf (the implementation that we are actually using in Sage) does not
have a --debug switch.
--
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: git diff branch1..develop
On 2014-05-01, Simon King wrote: > Hi! > > Next question: > > On 2014-05-01, Simon King wrote: >> I immediately started playing with it, and I wonder: Can I configure >> it so that "git trac review 12345" shows me the diff in "less" (or another >> pager)? git does use "less" when I call "git log" or "git diff ...", but >> I don't see any hint in ~/.gitconfig why less is used on the log and the >> diff but not on "trac review". > > Why am I asked for my trac password when I just pull? Shouldn't a > password only be required for pushing, but not for pulling? did you look at http://boxen.math.washington.edu/home/vbraun/doc/developer/git_trac.html#section-git-trac-readonly ? It also seems that you'd only need to do git trac config --user USERNAME --pass 'PASSWORD' once, and it will store the data somewhere... -- 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: R graphics and pkg-config (trac #15742)
On Thursday, May 1, 2014 9:58:47 PM UTC+1, leif wrote: > > > pkg-config --variable pc_path pkg-config > That doesn't always work. (See my other post on how to get it.) > Where does it not work? -- 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: git diff branch1..develop
Simon King wrote: Why am I asked for my trac password when I just pull? Shouldn't a password only be required for pushing, but not for pulling? Depends on the configured protocol (I think); git://... vs. ssh://git@... -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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: R graphics and pkg-config (trac #15742)
It does have a configure option: $ ./configure --help `configure' configures pkgconf 0.9.4 to adapt to many kinds of systems. [...] --with-pkg-config-dir specify the place where pc files will be found On Thursday, May 1, 2014 10:45:12 PM UTC+1, leif wrote: > > Well, we could just patch our pkgconf; it apparently hasn't a configure > option to set the default search path, but hardcodes > Fix at http://trac.sagemath.org/ticket/16274 -- 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: git diff branch1..develop
Hi! Next question: On 2014-05-01, Simon King wrote: > I immediately started playing with it, and I wonder: Can I configure > it so that "git trac review 12345" shows me the diff in "less" (or another > pager)? git does use "less" when I call "git log" or "git diff ...", but > I don't see any hint in ~/.gitconfig why less is used on the log and the > diff but not on "trac review". Why am I asked for my trac password when I just pull? Shouldn't a password only be required for pushing, but not for pulling? Best regards, Simon -- 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: R graphics and pkg-config (trac #15742)
François Bissey wrote:
On Thu, 01 May 2014 23:06:53 leif wrote:
François Bissey wrote:
On Thu, 01 May 2014 22:58:47 leif wrote:
Felix Salfelder wrote:
pkg-config --variable pc_path pkg-config
That doesn't always work. (See my other post on how to get it.)
Using configure is certainly a good option. +1, I like it.
Sage's top-level 'configure' or pkg-config's?
sage's configure.
Well, we could just patch our pkgconf; it apparently hasn't a configure
option to set the default search path, but hardcodes
-DPKG_DEFAULT_PATH=\"${pkgconfigdir}\"
in Makefile.in.
So we could look up a system's pkg-config path in its spkg-install, and
append it to our pkgconf's.
(Unfortunately sage-env currently doesn't save the original setting of
PATH though, AFAICS, so we'd have to do that as well.)
We could put it into sage-env as well, but regarding how often that's
called...
I was actually thinking of feeding it to sage-env :)
? sage-env.in?
The problem is that it's under revision control of course, but we could
there source some $SAGE_ROOT/local/var/lib/sage/system_pkg-config_path
if it exists...
I gave up with 'sed' (due to shell escape weirdness), but we'd have to
use $AWK (or @AWK@) otherwise to stay portable.
And "sed -i" is a GNU extension, that is one of the pains I have dealing
with AIX.
On Solaris as well...
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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: R graphics and pkg-config (trac #15742)
On Thu, 01 May 2014 23:06:53 leif wrote: > François Bissey wrote: > > On Thu, 01 May 2014 22:58:47 leif wrote: > >> Felix Salfelder wrote: > >>> pkg-config --variable pc_path pkg-config > >> > >> That doesn't always work. (See my other post on how to get it.) > > > > Using configure is certainly a good option. +1, I like it. > > Sage's top-level 'configure' or pkg-config's? > sage's configure. > We could put it into sage-env as well, but regarding how often that's > called... > I was actually thinking of feeding it to sage-env :) > I gave up with 'sed' (due to shell escape weirdness), but we'd have to > use $AWK (or @AWK@) otherwise to stay portable. > And "sed -i" is a GNU extension, that is one of the pains I have dealing with AIX. Francois -- 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: R graphics and pkg-config (trac #15742)
François Bissey wrote: On Thu, 01 May 2014 22:58:47 leif wrote: Felix Salfelder wrote: pkg-config --variable pc_path pkg-config That doesn't always work. (See my other post on how to get it.) Using configure is certainly a good option. +1, I like it. Sage's top-level 'configure' or pkg-config's? We could put it into sage-env as well, but regarding how often that's called... I gave up with 'sed' (due to shell escape weirdness), but we'd have to use $AWK (or @AWK@) otherwise to stay portable. -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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: git diff branch1..develop
Hi Dima, On 2014-05-01, Dima Pasechnik wrote: >> What does one need to do to get the git-trac script, and where is it >> documented? > http://boxen.math.washington.edu/home/vbraun/doc/developer/git_trac.html#installing-the-git-trac-command Great, thank you! I immediately started playing with it, and I wonder: Can I configure it so that "git trac review 12345" shows me the diff in "less" (or another pager)? git does use "less" when I call "git log" or "git diff ...", but I don't see any hint in ~/.gitconfig why less is used on the log and the diff but not on "trac review". Cheers, Simon -- 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: R graphics and pkg-config (trac #15742)
On Thu, 01 May 2014 22:58:47 leif wrote: > Felix Salfelder wrote: > > pkg-config --variable pc_path pkg-config > > That doesn't always work. (See my other post on how to get it.) > > Using configure is certainly a good option. +1, I like it. Francois -- 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: R graphics and pkg-config (trac #15742)
Felix Salfelder wrote: pkg-config --variable pc_path pkg-config That doesn't always work. (See my other post on how to get it.) -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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: R graphics and pkg-config (trac #15742)
Francois Bissey wrote:
That's a serious issue that Volker and I have overlooked when pushing
for pkg-config. For those who don't the tipping point for inclusion
was building recent matplotlib in OS X. matplotlib absolutely relies
on using pkgconfig and all the previous work around failed with 1.3.1.
At which point we decided the easiest solution was inclusion of
pkgconfig.
Now to fix this, and I believe you are right that this is a blocker, I
think we should change the way we override PKG_CONFIG_PATH
in sage-env. pkgconfig usually has a hardcoded internal value for
system install so you are able to find system packages without the variable
having to be defined. We are breaking that.
So we should either find the system folders in sage-env or patch our
pkgconfig source to search them automagically.
As a work around that doesn't involve moving things around defining
PKG_CONFIG_PATH=/usr/lib{64}/pkgconfig
before running make should help.
We could do that automagically (if pkg-config is installed system-wide,
which Sage's 'configure' or our pkg-config's spkg-install should
probably check).
$ pkg-config --debug 2>&1 | awk '/^Scanning /{print
substr($3,2,length($3)-2)}'
/usr/local/lib/pkgconfig
/usr/lib/pkgconfig
/usr/share/pkgconfig
-leif
On 2/05/2014, at 5:38, William Stein wrote:
Hi,
I just spent a while trying to figure out how to get R png graphics to
work again in Sage-6.2rc0 on Ubuntu 14.04. Note that graphics worked
fine with Sage-6.2beta1 on Ubuntu 12.04.Karl Dieter's many random
posts around the web asking about this problem were helpful, though in
this case the problem is new in sage-6.2rc0 due to trac #15742, and
will kill R usage for a lot of people if we release sage-6.2.rc0 as
is...
I tracked the problem down to pkg-config being in Sage-6.2rc0, whereas
it is not in Sage-6.2beta1.
This is because of http://trac.sagemath.org/ticket/15742, which is
very important to getting Sage to build at all on some wonky systems.
But on a mainstream modern Linux OS this ticket leads to problems.
Wouldn't it be better to only build/install pkgconfig on systems that
don't have a good one already?
My solution to deal with this R problem is:
cd $SAGE_ROOT/local/bin && mv pkg-config pkg-config.orig && ln -s
/usr/bin/pkg-config .
sage -f r
Of course, I have to wonder what other components of Sage got built
incorrectly due to Sage's pkg-config returning misleading results
(e.g., saying that a system-wide library isn't available even though
it is)...
William
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
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: git diff branch1..develop
On 2014-05-01, Simon King wrote: > Hi Volker, > > On 2014-05-01, Volker Braun wrote: >> If you want to do it offline this is also implemented as "git trac review" >> in the git-trac script. > > What does one need to do to get the git-trac script, and where is it > documented? http://boxen.math.washington.edu/home/vbraun/doc/developer/git_trac.html#installing-the-git-trac-command HTH, Dima -- 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: git diff branch1..develop
On Thu, May 1, 2014 at 9:30 AM, leif wrote: > Travis Scrimshaw wrote: > >> That happens when you've started making a comment (or any other change >> to the ticket) as part of the preview. >> > > Hardly related, but is it intentional that trac meanwhile also colors (and > even strikes!) trac user names in replies / quotes (depending on or > according to the /state of the ticket/)? > No, this came about from upgrading our version of trac -- it seemed so minor that I didn't spend the time investigating it. > > Just asking... > > > -leif > > -- > () The ASCII Ribbon Campaign > /\ Help Cure HTML E-Mail > > > -- > 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. > -- Andrew -- 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] R graphics and pkg-config (trac #15742)
On Thu, May 01, 2014 at 07:18:18PM +, Francois Bissey wrote:
> So we should either find the system folders in sage-env or patch our
> pkgconfig source to search them automagically.
fwiw: last year i figured out the following values to make the
'configurable sage ("the distribution")' work.
PKG_CONFIG_PATH=`pkg-config --variable pc_path pkg-config`
PKG_CONFIG_LIBDIR="$path_where_local_is/local/lib/pkgconfig"
patching pkg-config doesnt seem to be necessary. you will somehow have
to call pkg-config before changing $PATH.
have fun
felix
--
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] R graphics and pkg-config (trac #15742)
I don't think there is a way to find out which path was compiled into the
system pkg-config binary. We should just make our pkg-config a script that
punts to the system pkg-config if the library is not in Sage.
On Thursday, May 1, 2014 8:18:18 PM UTC+1, François wrote:
>
> That’s a serious issue that Volker and I have overlooked when pushing
> for pkg-config. For those who don’t the tipping point for inclusion
> was building recent matplotlib in OS X. matplotlib absolutely relies
> on using pkgconfig and all the previous work around failed with 1.3.1.
> At which point we decided the easiest solution was inclusion of
> pkgconfig.
> Now to fix this, and I believe you are right that this is a blocker, I
> think we should change the way we override PKG_CONFIG_PATH
> in sage-env. pkgconfig usually has a hardcoded internal value for
> system install so you are able to find system packages without the
> variable
> having to be defined. We are breaking that.
> So we should either find the system folders in sage-env or patch our
> pkgconfig source to search them automagically.
>
> As a work around that doesn’t involve moving things around defining
> PKG_CONFIG_PATH=/usr/lib{64}/pkgconfig
> before running make should help.
>
> Francois
> On 2/05/2014, at 5:38, William Stein >
> wrote:
>
> > Hi,
> >
> > I just spent a while trying to figure out how to get R png graphics to
> > work again in Sage-6.2rc0 on Ubuntu 14.04. Note that graphics worked
> > fine with Sage-6.2beta1 on Ubuntu 12.04.Karl Dieter's many random
> > posts around the web asking about this problem were helpful, though in
> > this case the problem is new in sage-6.2rc0 due to trac #15742, and
> > will kill R usage for a lot of people if we release sage-6.2.rc0 as
> > is...
> >
> > I tracked the problem down to pkg-config being in Sage-6.2rc0, whereas
> > it is not in Sage-6.2beta1.
> >
> > This is because of http://trac.sagemath.org/ticket/15742, which is
> > very important to getting Sage to build at all on some wonky systems.
> > But on a mainstream modern Linux OS this ticket leads to problems.
> > Wouldn't it be better to only build/install pkgconfig on systems that
> > don't have a good one already?
> >
> > My solution to deal with this R problem is:
> >
> > cd $SAGE_ROOT/local/bin && mv pkg-config pkg-config.orig && ln -s
> > /usr/bin/pkg-config .
> > sage -f r
> >
> > Of course, I have to wonder what other components of Sage got built
> > incorrectly due to Sage's pkg-config returning misleading results
> > (e.g., saying that a system-wide library isn't available even though
> > it is)...
> >
> > 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 group and stop receiving emails from it, send
> an email to sage-devel+...@googlegroups.com .
> > To post to this group, send email to
> > sage-...@googlegroups.com.
>
> > Visit this group at http://groups.google.com/group/sage-devel.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> This email may be confidential and subject to legal privilege, it may
> not reflect the views of the University of Canterbury, and it is not
> guaranteed to be virus free. If you are not an intended recipient,
> please notify the sender immediately and erase all copies of the message
> and any attachments.
>
> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
> information.
>
--
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: README.txt
Updated README.txt: http://trac.sagemath.org/ticket/16273 -- 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] R graphics and pkg-config (trac #15742)
That's a serious issue that Volker and I have overlooked when pushing
for pkg-config. For those who don't the tipping point for inclusion
was building recent matplotlib in OS X. matplotlib absolutely relies
on using pkgconfig and all the previous work around failed with 1.3.1.
At which point we decided the easiest solution was inclusion of
pkgconfig.
Now to fix this, and I believe you are right that this is a blocker, I
think we should change the way we override PKG_CONFIG_PATH
in sage-env. pkgconfig usually has a hardcoded internal value for
system install so you are able to find system packages without the variable
having to be defined. We are breaking that.
So we should either find the system folders in sage-env or patch our
pkgconfig source to search them automagically.
As a work around that doesn't involve moving things around defining
PKG_CONFIG_PATH=/usr/lib{64}/pkgconfig
before running make should help.
Francois
On 2/05/2014, at 5:38, William Stein wrote:
> Hi,
>
> I just spent a while trying to figure out how to get R png graphics to
> work again in Sage-6.2rc0 on Ubuntu 14.04. Note that graphics worked
> fine with Sage-6.2beta1 on Ubuntu 12.04.Karl Dieter's many random
> posts around the web asking about this problem were helpful, though in
> this case the problem is new in sage-6.2rc0 due to trac #15742, and
> will kill R usage for a lot of people if we release sage-6.2.rc0 as
> is...
>
> I tracked the problem down to pkg-config being in Sage-6.2rc0, whereas
> it is not in Sage-6.2beta1.
>
> This is because of http://trac.sagemath.org/ticket/15742, which is
> very important to getting Sage to build at all on some wonky systems.
> But on a mainstream modern Linux OS this ticket leads to problems.
> Wouldn't it be better to only build/install pkgconfig on systems that
> don't have a good one already?
>
> My solution to deal with this R problem is:
>
> cd $SAGE_ROOT/local/bin && mv pkg-config pkg-config.orig && ln -s
> /usr/bin/pkg-config .
> sage -f r
>
> Of course, I have to wonder what other components of Sage got built
> incorrectly due to Sage's pkg-config returning misleading results
> (e.g., saying that a system-wide library isn't available even though
> it is)...
>
> 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 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.
This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.
Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.
--
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] Fwd: Re: README.txt
-- Forwarded message -- From: "R. Andrew Ohana" Date: May 1, 2014 11:50 AM Subject: Re: README.txt To: "William Stein" Cc: Most of what you are looking for is here: http://sagemath.org/doc/developer/coding_basics.html#files-and-directory-structure (The actual directory tree is new, and essentially ripped from the git SEP.) Where packages are built is determined by the environment variable SAGE_BUILD_DIR (if I recall directly), which has a default value that may, our may not be properly documented. On May 1, 2014 11:18 AM, "William Stein" wrote: > Hi, > > I still don't know my way around the completely re-organized sage-6+. > I constantly have questions like: > >- where is the temporary build directory when installing packages? > (used to be spkg/build) >- where are packages stored? (used to be spkg/standard or > spkg/optional) >- where are the databases? (used to be data/) >- where is the sage library source code? (used to be devel/sage). > > Literally every single answer is different now than it used to be. I > thought -- heh, maybe the answers are enumerated in README.txt now, > since some of them used to be there.Upon looking in sage-6.2.rc0, > not only did I not find the new answers, I found old answers, e.g., > > salvus@compute18dc0:/usr/local/sage/current$ tail README.txt > Almost every spkg in $SAGE_ROOT/spkg/standard/ is a bzip2-compressed > tarball (currently, the only exception is the bzip2 spkg itself, which > [...] > > The next natural place to look would be the Sage Developer's guide, > but I couldn't find any answers there. > > I can of course figure out the answers to the above questions using > find, grep, looking at the Makefile, etc., and actually *have done > that* several times already. However, since the answers are what is > canonical in maybe Andrew Ohana's mind, but not mine, they never > stick, and I can't remember any of them yet. I find it totally > arbitrary -- which is fine, if answers to questions like the above are > instant to find. > > Probably the answer to what the layout is, is in a trac ticket or wiki > page. I have no idea. I vaguely recall Andrew explaining it to me in > person once or twice. > > Anyway, I think the README.txt should be (1) correct -- not telling us > how it used to be (obviously), and (2) answer all questions like the > ones above. What are your questions about "where stuff is"? > > -- 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 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] README.txt
Hi, I still don't know my way around the completely re-organized sage-6+. I constantly have questions like: - where is the temporary build directory when installing packages? (used to be spkg/build) - where are packages stored? (used to be spkg/standard or spkg/optional) - where are the databases? (used to be data/) - where is the sage library source code? (used to be devel/sage). Literally every single answer is different now than it used to be. I thought -- heh, maybe the answers are enumerated in README.txt now, since some of them used to be there.Upon looking in sage-6.2.rc0, not only did I not find the new answers, I found old answers, e.g., salvus@compute18dc0:/usr/local/sage/current$ tail README.txt Almost every spkg in $SAGE_ROOT/spkg/standard/ is a bzip2-compressed tarball (currently, the only exception is the bzip2 spkg itself, which [...] The next natural place to look would be the Sage Developer's guide, but I couldn't find any answers there. I can of course figure out the answers to the above questions using find, grep, looking at the Makefile, etc., and actually *have done that* several times already. However, since the answers are what is canonical in maybe Andrew Ohana's mind, but not mine, they never stick, and I can't remember any of them yet. I find it totally arbitrary -- which is fine, if answers to questions like the above are instant to find. Probably the answer to what the layout is, is in a trac ticket or wiki page. I have no idea. I vaguely recall Andrew explaining it to me in person once or twice. Anyway, I think the README.txt should be (1) correct -- not telling us how it used to be (obviously), and (2) answer all questions like the ones above. What are your questions about "where stuff is"? -- 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 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] R graphics and pkg-config (trac #15742)
Hi, I just spent a while trying to figure out how to get R png graphics to work again in Sage-6.2rc0 on Ubuntu 14.04. Note that graphics worked fine with Sage-6.2beta1 on Ubuntu 12.04.Karl Dieter's many random posts around the web asking about this problem were helpful, though in this case the problem is new in sage-6.2rc0 due to trac #15742, and will kill R usage for a lot of people if we release sage-6.2.rc0 as is... I tracked the problem down to pkg-config being in Sage-6.2rc0, whereas it is not in Sage-6.2beta1. This is because of http://trac.sagemath.org/ticket/15742, which is very important to getting Sage to build at all on some wonky systems. But on a mainstream modern Linux OS this ticket leads to problems. Wouldn't it be better to only build/install pkgconfig on systems that don't have a good one already? My solution to deal with this R problem is: cd $SAGE_ROOT/local/bin && mv pkg-config pkg-config.orig && ln -s /usr/bin/pkg-config . sage -f r Of course, I have to wonder what other components of Sage got built incorrectly due to Sage's pkg-config returning misleading results (e.g., saying that a system-wide library isn't available even though it is)... 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 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: git diff branch1..develop
Travis Scrimshaw wrote: That happens when you've started making a comment (or any other change to the ticket) as part of the preview. Hardly related, but is it intentional that trac meanwhile also colors (and even strikes!) trac user names in replies / quotes (depending on or according to the /state of the ticket/)? Just asking... -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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 compiling sage 6.2.rc0-develop with macosx/mavericks
kcrisman wrote: Though Merged in is still a useful field ;-) Couldn't a script update all newly merged tickets after each release (including devel releases)? I have no idea, but recall that Minh used to run a script to update the Milestone fields (everytime a new stable version had been released). -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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: Requests in Sage?
Hi Volker, hi William, On 2014-05-01, Volker Braun wrote: > AFAIK we don't do anything to break urllib in doctests, so if it works on > the commandline but not in doctests then its likely that the server limits > the request rate. It is all very strange. The test suite of the cohomology spkg runs "sage -t" on some temporary files generated from the docs. So, I put the failing test into a file and tested it separately---but "sage -t" had no complains. I am now re-running the full test suite of the package again, to see if the three unsuccessful previous attempts have just been temporary problems. Best regards, Simon -- 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] Hoping to develop Game Theoretical capabilities in to Sage
On Wed, Apr 30, 2014 at 8:36 AM, Vincent Knight wrote: > Dear all, > > I am attempting to follow the developer guidelines and after applying for a > trac server account it is recommended to email this list with some details > of what I hope to do before opening a ticket. > > If it sounds like a good idea I'd like to open tickets with an aim to > develop some Game Theoretic capabilities in to Sage. Loosely this would > include the following: > > - A general class for a general game object, > - Classes for cooperative games, > - Class for matching games > - Classes for normal form games, > > Most of this is relatively simple to do however methods to solve normal form > games would require new algorithms to be written and/or and adaption of the > lrs package (http://cgm.cs.mcgill.ca/~avis/C/lrs.html) (that I understand > 'lives' in Sage already somewhere...) > > I (think I) understand that I would need to open multiple tickets for this > and suggest opening 3 tickets (one for each of the types of game so far). > > I have obtained funding to have a talented undergraduate student (proficient > with Python, Sage, git and starting to learn Cython as well as various other > tools) work with me on this over the summer. Proposal available here: > http://goo.gl/4ck47Q > > As a result of this I am thinking about potentially taking the student to > present at a national UK conference where we would showcase not only the > Game Theory code but also Sage as a research tool. > > In the future this could/would hopefully lead to more types of game > theoretic models being added. > > I'm not sure if this was the type of email I was expected to write but > hopefully everyone thinks this is an ok idea as I am impatient to be able to > call myself a contributor to Sage :) > > I'd be grateful to hear your thoughts. Something called "gambit" comes up a lot upon searching for "game theory" and python on google. Gambit seems to have a mature Python library interface, in version 14, and Gambit seems to have been around since 1994 (?). The first slogan of Sage has always been "building the car instead of reinventing the wheel". I would have guessed that you know all about Gambit and why totally ignoring it for Sage is the way to go, but you say: "You might also want to check out 'Gambit' which I've never used." at http://stackoverflow.com/questions/4901549/nash-equilibrium-in-python so ... maybe it would be worth you checking out Gambit first? Sorry if this wasn't very helpful regarding your actual questions. Caveat: I've never used Gambit either! -- William > > Best wishes, > Vince > > -- > Dr Vincent Knight > Cardiff School of Mathematics > Senghennydd Road, > Cardiff > CF24 4AG > (+44) 29 2087 5548 > www.vincent-knight.com > +Vincent Knight > @drvinceknight > Skype: drvinceknight > > -- > 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. -- 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 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] Hoping to develop Game Theoretical capabilities in to Sage
Dear all, I am attempting to follow the developer guidelines and after applying for a trac server account it is recommended to email this list with some details of what I hope to do before opening a ticket. If it sounds like a good idea I'd like to open tickets with an aim to develop some Game Theoretic capabilities in to Sage. Loosely this would include the following: - A general class for a general game object, - Classes for cooperative games, - Class for matching games - Classes for normal form games, Most of this is relatively simple to do however methods to solve normal form games would require new algorithms to be written and/or and adaption of the lrs package (http://cgm.cs.mcgill.ca/~avis/C/lrs.html) (that I understand 'lives' in Sage already somewhere...) I (think I) understand that I would need to open multiple tickets for this and suggest opening 3 tickets (one for each of the types of game so far). I have obtained funding to have a talented undergraduate student (proficient with Python, Sage, git and starting to learn Cython as well as various other tools) work with me on this over the summer. Proposal available here: http://goo.gl/4ck47Q As a result of this I am thinking about potentially taking the student to present at a national UK conference where we would showcase not only the Game Theory code but also Sage as a research tool. In the future this could/would hopefully lead to more types of game theoretic models being added. I'm not sure if this was the type of email I was expected to write but hopefully everyone thinks this is an ok idea as I am impatient to be able to call myself a contributor to Sage :) I'd be grateful to hear your thoughts. Best wishes, Vince -- Dr Vincent Knight Cardiff School of Mathematics Senghennydd Road, Cardiff CF24 4AG (+44) 29 2087 5548 www.vincent-knight.com +Vincent Knight @drvinceknight Skype: drvinceknight -- 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] Requests in Sage?
On Thu, May 1, 2014 at 7:43 AM, Simon King wrote: > Hi! > > Currently, I have problems with web-accessing doctests in my modular > group cohomology package for Sage. These tests used to work (of course > provided that there is an internet connection), but fail now with a > timeout. > > Trying to find the underlying reason, I found that meanwhile people seem > to recommend the "requests" module and think that urllib2 (which I am > using in the package) should be replaced by requests. No idea if this > would solve my problem, but perhaps it would make sense to try. > > What do people here think about requests? I used requests a lot at one point last year (when I was writing SMC in Python rather than Node.js), and was very impressed. It's much better than urllib2. I'm installing it by default on SMC as well. That said, I'm always very reluctant to add new packages to Sage -- they will cause extra maintenance work, complexity, and pain. And if nothing in the core of Sage really relies on them, then they probably shouldn't be in Sage. I would prefer to add "pip" to Sage, and let users do "pip install requests" than to add requests to sage. > It is Apache2 Licensed; would > this be compatible with Sage's license? Yes, though only because we switched to GPLv2+, since Apache is *not* GPLv2 compatible. See http://www.apache.org/licenses/GPL-compatibility.html I'm just answering your questions. As Volker says, using requests is probably not going to solve your problem though. William > > Best regards, > Simon > > > -- > 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. -- 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 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: Requests in Sage?
urllib is a standard Python component and basically (up to some trivial reorganization) also part of Py3. Its not going to go away. Requests is a nice add-on package but I don't think its going to fix your problem. AFAIK we don't do anything to break urllib in doctests, so if it works on the commandline but not in doctests then its likely that the server limits the request rate. On Thursday, May 1, 2014 3:43:21 PM UTC+1, Simon King wrote: > > Hi! > > Currently, I have problems with web-accessing doctests in my modular > group cohomology package for Sage. These tests used to work (of course > provided that there is an internet connection), but fail now with a > timeout. > > Trying to find the underlying reason, I found that meanwhile people seem > to recommend the "requests" module and think that urllib2 (which I am > using in the package) should be replaced by requests. No idea if this > would solve my problem, but perhaps it would make sense to try. > > What do people here think about requests? It is Apache2 Licensed; would > this be compatible with Sage's license? > > Best regards, > Simon > > > -- 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: git diff branch1..develop
That happens when you've started making a comment (or any other change to the ticket) as part of the preview. Best, Travis On Thursday, May 1, 2014 6:25:31 AM UTC-7, Volker Braun wrote: > > I've seen that occasionally, if you leave a trac window open for a long > time then sometimes the ticket name is no longer a link. I don't know > exactly what triggers it, possibly when the ticket is updated by somebody > else (ajax call?). In any case its easily fixed by reloading the page. > > > > On Thursday, May 1, 2014 1:17:38 PM UTC+1, John Cremona wrote: >> >> In my browser (firefox) viewing http://trac.sagemath.org/ticket/15976 >> (and logged in), the "public/ticket/15976" was not a link! >> > -- 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] Requests in Sage?
Hi! Currently, I have problems with web-accessing doctests in my modular group cohomology package for Sage. These tests used to work (of course provided that there is an internet connection), but fail now with a timeout. Trying to find the underlying reason, I found that meanwhile people seem to recommend the "requests" module and think that urllib2 (which I am using in the package) should be replaced by requests. No idea if this would solve my problem, but perhaps it would make sense to try. What do people here think about requests? It is Apache2 Licensed; would this be compatible with Sage's license? Best regards, Simon -- 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: Web access during doctests?
Hi Vincent, On 2014-05-01, Vincent Delecroix <20100.delecr...@gmail.com> wrote: >> Does oeis.py rely on urllib2 as well? > > Arch. No. You are right. Only urllib (through the functions urlopen, > urlencode). Is there a fundamental difference between them? I don't know, that's partially why I ask. Best regards, Simon -- 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] Tracking a git branch
On Thursday, May 1, 2014 1:27:02 PM UTC+1, KnS wrote: > > while if I set the "default remote branch" to trac/develop or something > like that, I could just say: > $ git pull > while in the branch, right? > Correct. The "git trac" script sets that up automatically if you use it to download a branch: $ git trac checkout develop $ git branch -vv * develop fc52070 [trac/develop] Updated Sage version to 6.2.rc1 master 3472a85 [origin/master] Updated Sage version to 6.0 -- 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: Web access during doctests?
2014-05-01 15:19 UTC+02:00, Simon King : > Hi Vincent, > > On 2014-05-01, Vincent Delecroix <20100.delecr...@gmail.com> wrote: >> I had no problem with accessing internet from doctest during my work >> on #16252. You can try to run >> >> $ sage -t --optional=sage,internet SAGE_ROOT/src/sage/databases/oeis.py >> >> and see if you got any timeout (I don't). > > I get numerous errors, and in the end my browser is made to show some > oeis page, but there is no timeout at all. This is normal... and the reason of #16252... But at least, you have access to internet during the doctests. > Does oeis.py rely on urllib2 as well? Arch. No. You are right. Only urllib (through the functions urlopen, urlencode). Is there a fundamental difference between them? Best, Vincent -- 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: git diff branch1..develop
I've seen that occasionally, if you leave a trac window open for a long time then sometimes the ticket name is no longer a link. I don't know exactly what triggers it, possibly when the ticket is updated by somebody else (ajax call?). In any case its easily fixed by reloading the page. On Thursday, May 1, 2014 1:17:38 PM UTC+1, John Cremona wrote: > > In my browser (firefox) viewing http://trac.sagemath.org/ticket/15976 > (and logged in), the "public/ticket/15976" was not a link! > -- 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: Web access during doctests?
Hi Vincent, On 2014-05-01, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > I had no problem with accessing internet from doctest during my work > on #16252. You can try to run > > $ sage -t --optional=sage,internet SAGE_ROOT/src/sage/databases/oeis.py > > and see if you got any timeout (I don't). I get numerous errors, and in the end my browser is made to show some oeis page, but there is no timeout at all. Does oeis.py rely on urllib2 as well? Best regards, Simon -- 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] Tracking a git branch
You are right. You can edit the config (.git/config) to set it up once for all and this is answered for example in http://stackoverflow.com/questions/658885/how-do-you-get-git-to-always-pull-from-a-specific-branch 2014-05-01 14:27 UTC+02:00, Kannappan Sampath : > But everytime I need to update, I will have to do > > $ git pull trac develop > > while if I set the "default remote branch" to trac/develop or something > like that, I could just say: > > $ git pull > > while in the branch, right? > > Am I missing something, in that, there is something called tracking a > remote branch as described in "Tracking Branches" section here: > http://git-scm.com/book/en/Git-Branching-Remote-Branches? > > With Sincere Regards, > Kannappan. > > > On Thu, May 1, 2014 at 4:01 PM, Vincent Delecroix > <20100.delecr...@gmail.com >> wrote: > >> Of course, I assumed that you have trac declared as a remote git >> server. You can check that with >> >> $ git remote -v >> trac g...@trac.sagemath.org:sage.git (fetch) >> trac g...@trac.sagemath.org:sage.git (push) >> >> 2014-05-01 12:29 UTC+02:00, Vincent Delecroix >> <20100.delecr...@gmail.com>: >> > Hi, >> > >> > Be sure that you are in your develop branch on your machine. Then do >> > >> > $ git pull trac develop >> > >> > Or alternatively >> > >> > $ git fetch trac develop >> > $ git merge FETCH_HEAD >> > >> > That way your local branch get updated with the one on trac. >> > >> > Vincent >> > >> > 2014-05-01 12:26 UTC+02:00, Kannappan Sampath : >> >> Hello sage-devel: >> >> >> >> Nathann has kindly helped me a lot making me feel at home with >> >> git+sage >> >> stuff. I have one problem facing me. I have a local "develop" branch. >> >> I >> >> would like that to track the remote trac's develop branch... >> >> >> >> How do I do this? >> >> >> >> With Sincere regards, >> >> Kannappan. >> >> >> >> -- >> >> 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. >> >> >> > >> >> -- >> 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. >> > > -- > 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. > -- 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] Tracking a git branch
But everytime I need to update, I will have to do $ git pull trac develop while if I set the "default remote branch" to trac/develop or something like that, I could just say: $ git pull while in the branch, right? Am I missing something, in that, there is something called tracking a remote branch as described in "Tracking Branches" section here: http://git-scm.com/book/en/Git-Branching-Remote-Branches? With Sincere Regards, Kannappan. On Thu, May 1, 2014 at 4:01 PM, Vincent Delecroix <20100.delecr...@gmail.com > wrote: > Of course, I assumed that you have trac declared as a remote git > server. You can check that with > > $ git remote -v > trac g...@trac.sagemath.org:sage.git (fetch) > trac g...@trac.sagemath.org:sage.git (push) > > 2014-05-01 12:29 UTC+02:00, Vincent Delecroix <20100.delecr...@gmail.com>: > > Hi, > > > > Be sure that you are in your develop branch on your machine. Then do > > > > $ git pull trac develop > > > > Or alternatively > > > > $ git fetch trac develop > > $ git merge FETCH_HEAD > > > > That way your local branch get updated with the one on trac. > > > > Vincent > > > > 2014-05-01 12:26 UTC+02:00, Kannappan Sampath : > >> Hello sage-devel: > >> > >> Nathann has kindly helped me a lot making me feel at home with git+sage > >> stuff. I have one problem facing me. I have a local "develop" branch. I > >> would like that to track the remote trac's develop branch... > >> > >> How do I do this? > >> > >> With Sincere regards, > >> Kannappan. > >> > >> -- > >> 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. > >> > > > > -- > 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. > -- 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: git diff branch1..develop
On 1 May 2014 12:37, Volker Braun wrote: > Ok, let me try again. If you go to http://trac.sagemath.org/ticket/15976 the > ticket says: > > Branch:public/ticket/15976 (Commits) > > If you click on "public/ticket/15976" then you see the cumulative diff In my browser (firefox) viewing http://trac.sagemath.org/ticket/15976 (and logged in), the "public/ticket/15976" was not a link! I think I would have found it otherwise. But I refeshed the page and now it is a link, and displays exactly as you say. So this is fine, and exactly what Marti nand I wanted to see; the only mystery is why that link was unlinked when I first looked at it. John > > If you click on "(Commits)" you'll see the individual commits. > > > On Thursday, May 1, 2014 12:32:57 PM UTC+1, John Cremona wrote: >> >> When I do that I see the list of about 15 commits with commit messages >> but not the diffs. I can clisck on any of these commits and see the >> diffs for that commit, but how do I see the cumulative diffs for the >> sequence of commits (in trac)? >> > -- > 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. -- 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] Web access during doctests?
2014-05-01 13:44 UTC+02:00, Simon King : > Hi! > > Until recently, it was possible to access internet in doctests. Of > course, such tests should be optional, however it is needed if one > has a function whose purpose is to access some data in the web. > > I noticed today that two tests in my group cohomology spkg fail with > URLError: > These tests used to work in older Sage versions, and also they work if I > do these tests manually in an interactive session (on the same machine, > and, yes, my laptop had internet connection while running the tests). > > So, I wonder if something has recently (last half year or so) changed in > the doctest framework that prevents urllib2 from working in doctests. I had no problem with accessing internet from doctest during my work on #16252. You can try to run $ sage -t --optional=sage,internet SAGE_ROOT/src/sage/databases/oeis.py and see if you got any timeout (I don't). Vincent -- 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] Web access during doctests?
Hi! Until recently, it was possible to access internet in doctests. Of course, such tests should be optional, however it is needed if one has a function whose purpose is to access some data in the web. I noticed today that two tests in my group cohomology spkg fail with URLError: These tests used to work in older Sage versions, and also they work if I do these tests manually in an interactive session (on the same machine, and, yes, my laptop had internet connection while running the tests). So, I wonder if something has recently (last half year or so) changed in the doctest framework that prevents urllib2 from working in doctests. Best regards, Simon -- 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: git diff branch1..develop
Ok, let me try again. If you go to http://trac.sagemath.org/ticket/15976 the ticket says: Branch:public/ticket/15976 (Commits) If you click on "public/ticket/15976" then you see the cumulative diff If you click on "(Commits)" you'll see the individual commits. On Thursday, May 1, 2014 12:32:57 PM UTC+1, John Cremona wrote: > > When I do that I see the list of about 15 commits with commit messages > but not the diffs. I can clisck on any of these commits and see the > diffs for that commit, but how do I see the cumulative diffs for the > sequence of commits (in trac)? > > -- 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: git diff branch1..develop
On 1 May 2014 12:08, Volker Braun wrote: > If you click on the branch name (not the "Commits") on trac then it'll show > you just the cumulative diff against the current develop branch. It actually > does the merge and then the diff from the merge, which is a bit more useful > than just git diff my_branch...develop. > When I do that I see the list of about 15 commits with commit messages but not the diffs. I can clisck on any of these commits and see the diffs for that commit, but how do I see the cumulative diffs for the sequence of commits (in trac)? John > If you want to do it offline this is also implemented as "git trac review" > in the git-trac script. > > > > > On Thursday, May 1, 2014 12:00:02 PM UTC+1, Martin Albrecht wrote: >> >> Hi all, >> >> currently it is a bit awkward to review a branch on trac which has many >> commits. For example >> >>http://trac.sagemath.org/ticket/15976 >> >> has quite a few commits so it seems quite daunting to review it, whereas >> the >> actual difference to the main development branch is not that much. >> Locally, we >> can do: >> >> $ git diff my_branch..develop >> >> and >> >> $ git diff my_branch...develop >> >> cf. >> https://stackoverflow.com/questions/9834689/comparing-two-branches-in-git >> >> Could something like this be added to trac? >> >> Cheers, >> Martin > > -- > 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. -- 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: git diff branch1..develop
Hi Volker, On 2014-05-01, Volker Braun wrote: > If you want to do it offline this is also implemented as "git trac review" > in the git-trac script. What does one need to do to get the git-trac script, and where is it documented? Cheers, Simon -- 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: git diff branch1..develop
If you click on the branch name (not the "Commits") on trac then it'll show you just the cumulative diff against the current develop branch. It actually does the merge and then the diff from the merge, which is a bit more useful than just git diff my_branch...develop. If you want to do it offline this is also implemented as "git trac review" in the git-trac script. On Thursday, May 1, 2014 12:00:02 PM UTC+1, Martin Albrecht wrote: > > Hi all, > > currently it is a bit awkward to review a branch on trac which has many > commits. For example > >http://trac.sagemath.org/ticket/15976 > > has quite a few commits so it seems quite daunting to review it, whereas > the > actual difference to the main development branch is not that much. > Locally, we > can do: > > $ git diff my_branch..develop > > and > > $ git diff my_branch...develop > > cf. > https://stackoverflow.com/questions/9834689/comparing-two-branches-in-git > > Could something like this be added to trac? > > Cheers, > Martin -- 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] git diff branch1..develop
2014-05-01 13:00 UTC+02:00, Martin Albrecht : > Hi all, > > currently it is a bit awkward to review a branch on trac which has many > commits. For example > >http://trac.sagemath.org/ticket/15976 > > has quite a few commits so it seems quite daunting to review it, whereas the > > actual difference to the main development branch is not that much. Locally, > we > can do: > > $ git diff my_branch..develop > > and > > $ git diff my_branch...develop > > cf. > https://stackoverflow.com/questions/9834689/comparing-two-branches-in-git > > Could something like this be added to trac? +1 And in the developer guide! I also learned from Volker $ git log my_branch ^develop which only selects commit in my_branch that do not belong to develop. Cheers Vincent -- 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] git diff branch1..develop
Hi all, currently it is a bit awkward to review a branch on trac which has many commits. For example http://trac.sagemath.org/ticket/15976 has quite a few commits so it seems quite daunting to review it, whereas the actual difference to the main development branch is not that much. Locally, we can do: $ git diff my_branch..develop and $ git diff my_branch...develop cf. https://stackoverflow.com/questions/9834689/comparing-two-branches-in-git Could something like this be added to trac? Cheers, Martin signature.asc Description: This is a digitally signed message part.
Re: [sage-devel] Tracking a git branch
Of course, I assumed that you have trac declared as a remote git server. You can check that with $ git remote -v trac g...@trac.sagemath.org:sage.git (fetch) trac g...@trac.sagemath.org:sage.git (push) 2014-05-01 12:29 UTC+02:00, Vincent Delecroix <20100.delecr...@gmail.com>: > Hi, > > Be sure that you are in your develop branch on your machine. Then do > > $ git pull trac develop > > Or alternatively > > $ git fetch trac develop > $ git merge FETCH_HEAD > > That way your local branch get updated with the one on trac. > > Vincent > > 2014-05-01 12:26 UTC+02:00, Kannappan Sampath : >> Hello sage-devel: >> >> Nathann has kindly helped me a lot making me feel at home with git+sage >> stuff. I have one problem facing me. I have a local "develop" branch. I >> would like that to track the remote trac's develop branch... >> >> How do I do this? >> >> With Sincere regards, >> Kannappan. >> >> -- >> 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. >> > -- 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] Tracking a git branch
Hi, Be sure that you are in your develop branch on your machine. Then do $ git pull trac develop Or alternatively $ git fetch trac develop $ git merge FETCH_HEAD That way your local branch get updated with the one on trac. Vincent 2014-05-01 12:26 UTC+02:00, Kannappan Sampath : > Hello sage-devel: > > Nathann has kindly helped me a lot making me feel at home with git+sage > stuff. I have one problem facing me. I have a local "develop" branch. I > would like that to track the remote trac's develop branch... > > How do I do this? > > With Sincere regards, > Kannappan. > > -- > 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. > -- 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] Tracking a git branch
Hello sage-devel: Nathann has kindly helped me a lot making me feel at home with git+sage stuff. I have one problem facing me. I have a local "develop" branch. I would like that to track the remote trac's develop branch... How do I do this? With Sincere regards, Kannappan. -- 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: Permutation groups and pickling
Hi Simon, Just a quick answer. On Thu, May 01, 2014 at 09:05:59AM +, Simon King wrote: > > - Implement a __reduce__ method to pickle by construction. > > This would mean to store the input parameters somewhere, which is likely > to create new memory leaks. There already is a .construction method which is functional. So there should be no obstruction here. In general, we are aiming toward having unique rep for as many parents as possible, and use pickling by construction whenever possible, right? As shown once again here pickling by class+data is brittle. So, are there any specific reason not to do it for permutation groups? And of course more parents if possible. Cheers, Nicolas -- Nicolas M. Thiéry "Isil" http://Nicolas.Thiery.name/ -- 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: Permutation groups and pickling
Hi Nicolas, On 2014-05-01, Nicolas M. Thiery wrote: > Analysis: the __setstate__ method of ParentWithGens does not store the > category whenever _element_constructor is not implemented. Funny. > Some approaches to fix this include: > > - Use UniqueRepresentation for permutation groups. > (with the side effect of them being pickled by construction). This would only fix this particular case. > - Implement a __reduce__ method to pickle by construction. This would mean to store the input parameters somewhere, which is likely to create new memory leaks. > - Implement an _element_constructor. Why isn't there, anyway? > - ... > > What's the best approach? Probably "...". What is the rationale for not storing the category when _element_constructor is not implemented? What has one to do with the other? I guess the underlying technical detail is that we have a Cython classes with cdef attributes (such as ._category or ._parent), and then derive a Python class from it. The Python class would by default way of pickling ignore anything that is not in __dict__. Hence, it would ignore ._category resp. ._parent. So, it may seem that we need a default __reduce__ method to deal with the cdef attributes. In the case of sage.categories.map.Map, we have these _extra_slots and _update_slots method that are supposed to be implemented in order to make some default __copy__ (or __reduce__) method work. I guess in principle this approach would work for ParentWithGens as well. But I am not so sure if this approach is nice. After all, how will you make people become aware that one needs not to implement __reduce__ but _update_slots and _extra_slots for pickling? Over several years (!), many maps could not be pickled, because no _update/extra_slots was implemented. Maps are fine now, by #14711, but how will you avoid similar things to happen again when providing a default __reduce__ that relies on custom methods that most Sage developers have never heard of? This may be related with Nathann's complaint about __mul__ relying on _mul_, _rmul_ and _lmul_. Best regards, Simon -- 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.
