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, Jo
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
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 rep
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 s
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.)
> >
> > W
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:
frb1
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 d
>
> 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 fro
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-tra
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 pu
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 grou
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
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
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 que
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-
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"
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.
T
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 r
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 p
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 hin
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 g
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
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-
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
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
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.
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
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.w
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
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.
PK
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 i
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
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 dec
-- 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 n
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 th
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 th
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
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 rel
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 r
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 go
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 Th
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 f
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 c
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
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
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.
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 bra
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/databa
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 Thu
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
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
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 bra
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:/
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
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 u
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
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 m
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 su
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 offli
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 differe
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,
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
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 sa
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
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 .constr
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.
> (wit
66 matches
Mail list logo
