On Sun, Sep 6, 2015 at 11:24 PM, William Stein wrote:
> On Sun, Sep 6, 2015 at 9:28 PM, Amy Feaver wrote:
>>
>>
>> I went through all of the pages under the "Images / Plotting / Art /
>> Interacts" links on the wiki and replaced the sagenb links with the cloud
>> ones. The only problem links I h
On Sun, Sep 6, 2015 at 9:28 PM, Amy Feaver wrote:
>
>
> I went through all of the pages under the "Images / Plotting / Art /
> Interacts" links on the wiki and replaced the sagenb links with the cloud
> ones. The only problem links I had were the ones originating from
> sagenb.mc.edu; this one fo
Frédéric Chapoton was removing tab characters from the description
field on lots of old tickets. He has since stopped, upon request.
There's a recent thread about an alternate solution to the problem he
was trying to solve.
David
On Mon, Sep 7, 2015 at 12:56 AM, Dr. David Kirkby (Kirkby Microwave
My inbox seems to be filling up with tons of emails about trac tickets I
opened years ago and were fixed years ago.
The following is an example of the probably 50-100 tickrts I have been
involved with.
http://trac.sagemath.org/ticket/9025
was opened 5 years ago, fixed and merged 5 years ago, but
I went through all of the pages under the "Images / Plotting / Art /
Interacts" links on the wiki and replaced the sagenb links with the cloud
ones. The only problem links I had were the ones originating from
sagenb.mc.edu;
this one for example:
http://sagenb.mc.edu/home/pub/97/
I can't find
Ah, yeah. That's a good place to start as an, I suppose!
--
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 g
Understood!
I'm just a comp sci undergrad who dabbles with math, so the chances of me
finding something that doesn't exist is slightly rare, I think :)
However, bugs I shall most definitely report
--
You received this message because you are subscribed to the Google Groups
"sage-devel" grou
Cool, thanks for handing me something concrete :)
--
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, s
On 09/07/15 06:33, Simon King wrote:
> Hi!
>
> Removing characters on trac has a positive side-effect: I was pointed
> to a ticket that was closed as duplicate of #5994. And the last serious work
> on #5994 was done 6 years ago.
>
> Unfortunately, I have marked it as "needs info" 6 years ago, an
On Sunday, September 6, 2015 at 11:29:14 PM UTC+2, Simon King wrote:
>
> Nice, thanks for the pointer! But would that work in a binary
> distribution (i.e., is "build" present in a binary distribution?)?
>
Well right now it is since a "binary" is just a tarred source tree with
artifacts.
What
Hi Volker,
On 2015-09-06, Volker Braun wrote:
> There is a canonical "version without patchlevel" provided by the
> sage_bootstrap library, nobody should re-implement "chopping off chars".
> E.g. (note the edge case):
>
> In [1]: import sys
> In [2]: sys.path.append('build')
> In [3]: from sag
Let me know if you need any pointers... My hint would be to load it into
an IPython session so you can make interactive trac queries. Then the rest
is easy.
On Sunday, September 6, 2015 at 10:34:08 PM UTC+2, Frédéric Chapoton wrote:
>
> using the XMLRPC query protocol
>
--
You received this m
There is a canonical "version without patchlevel" provided by the
sage_bootstrap library, nobody should re-implement "chopping off chars".
E.g. (note the edge case):
In [1]: import sys
In [2]: sys.path.append('build')
In [3]: from sage_bootstrap.package import Package
In [4]: Package('singular'
Hi Nathann,
On 2015-09-06, Nathann Cohen wrote:
> Can't we expect that the content of package-version.txt is *precisely*
> upstream's version, except for the ending .p0 or .p[number]? In which case
> we only have to strip that.
Singular's talkative version of a version is not just a version nu
Hi Jeroen,
On 2015-09-06, Jeroen Demeyer wrote:
> I don't think that package-version.txt should be used as answer to
> package.version() in Sage. I consider this file to be build metadata,
> while package.version() should provide upstream's idea of the version
> number, using some function or
Thanks Nathann,
I think I will rather go the way proposed by Volker, using the XMLRPC query
protocol.
This will take some work, but may have better side effects.
Frederic
Le dimanche 6 septembre 2015 21:33:17 UTC+2, Nathann Cohen a écrit :
>
> > well, one would have the same problem with comma
>
> I don't think that package-version.txt should be used as answer to
> package.version() in Sage. I consider this file to be build metadata,
> while package.version() should provide upstream's idea of the version
> number, using some function or data from the upstream sources.
>
Can't we ex
On 2015-09-06 20:33, Simon King wrote:
First question: Would you agree that all interfaces should return a
string that corresponds to the typical content of the
package-version.txt files?
No.
I don't think that package-version.txt should be used as answer to
package.version() in Sage. I consid
> well, one would have the same problem with commas...
No, because a long string that contains commas is surrounded by "...".
Now, you tell me that it becomes a problem if you have " characters in
the message? No, because it becomes "" (see
http://trac.sagemath.org/ticket/19149?format=csv)
This
well, one would have the same problem with commas...
Le dimanche 6 septembre 2015 21:11:10 UTC+2, William a écrit :
>
> On Sun, Sep 6, 2015 at 12:06 PM, Nathann Cohen > wrote:
> >> No, there is nothing like that, no easy way to guess the separations.
> >>
> >> Take a random ticket say 14090,
On Sun, Sep 6, 2015 at 12:06 PM, Nathann Cohen wrote:
>> No, there is nothing like that, no easy way to guess the separations.
>>
>> Take a random ticket say 14090, and look at
>> http://trac.sagemath.org/ticket/14090?format=tab
>
> Wow. Ugly indeed.
Why not change the bot to use
http://tra
I'm pretty sure you can get the info from the trac xmlrpc interface. The
data is xml-encoded so there is no problem with tabs. You can find example
code in the "git trac" command.
On Sunday, September 6, 2015 at 9:00:46 PM UTC+2, Frédéric Chapoton wrote:
>
> No, there is nothing like that, no
> No, there is nothing like that, no easy way to guess the separations.
>
> Take a random ticket say 14090, and look at
> http://trac.sagemath.org/ticket/14090?format=tab
Wow. Ugly indeed.
I do not know how it is obtained, but the output of "git trac print 14090"
looks much easier to parse. See
No, there is nothing like that, no easy way to guess the separations.
Take a random ticket say 14090, and look
at http://trac.sagemath.org/ticket/14090?format=tab
Frederic
Le dimanche 6 septembre 2015 20:31:03 UTC+2, Nathann Cohen a écrit :
>
> Well, trac does not offer any other sensible way
Gotcha, thanks :) I'll do some link replacing!
--
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
Hi!
Removing characters on trac has a positive side-effect: I was pointed
to a ticket that was closed as duplicate of #5994. And the last serious work
on #5994 was done 6 years ago.
Unfortunately, I have marked it as "needs info" 6 years ago, and
although I reminded the participants of the ticke
>
> Well, trac does not offer any other sensible way to extract info from the
> web pages of tickets (no json, only tsv (TAB separated values), and other
> stupid formats)
>
Isn't there some text that always appears before the description, as well
as some text [1] that appears right after it (
We still have some funding for
http://wiki.sagemath.org/days70
Does anybody else really want to go to Berkeley in November for a
Sage/Ipython workshop?
--
William (http://wstein.org)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubs
Hi William,
On 2015-09-06, William Stein wrote:
> Does anybody know why I'm getting hundreds (?) of email messages from
> trac today...? Is anybody else?
Not 100, but some.
The messages have in common that user "chapoton" changed the
documentation of closed(!) tickets, apparently by removing
Hi Jori,
On 2015-09-06, Jori =?ISO-8859-1?Q?M=E4ntysalo?= wrote:
> Should there be explicit way to say "I am just reporting this. I will not
> make nor review a patch."?
Well, if you open a ticket, then your name appears in the "Reporter"
field. However, the fields "Authors" and "Reviewers" rem
On Sun, Sep 6, 2015 at 10:46 AM, Amy Feaver wrote:
>
> Thanks everyone!
>
> I have to ask a couple questions before I go in and mess something up due to
> a lack of understanding :P But I'm happy to go through and do some
> link-replacing once I know what I'm doing.
>
> Should I simply be replacin
Well, trac does not offer any other sensible way to extract info from the
web pages of tickets (no json, only tsv (TAB separated values), and other
stupid formats)
Frederic
Le dimanche 6 septembre 2015 19:54:35 UTC+2, William a écrit :
>
> On Sun, Sep 6, 2015 at 10:46 AM, Frédéric Chapoton > w
On Sun, Sep 6, 2015 at 10:46 AM, Frédéric Chapoton wrote:
> Ok, I am stopping now. Sorry.
>
> But the bot cannot do the strip. It communicates with trac by using TAB as
> separators.
Maybe the communication shouldn't use TAB as a separator?
> So any TAB in the field description breaks the channe
Thanks everyone!
I have to ask a couple questions before I go in and mess something up due
to a lack of understanding :P But I'm happy to go through and do some
link-replacing once I know what I'm doing.
Should I simply be replacing the links from the notebook with the links
from the cloud? Or
Thanks everyone!
I have to ask a couple questions before I go in and mess something up due
to a lack of understanding :P But I'm happy to go through and do some
link-replacing once I know what I'm doing.
Should I simply be replacing the links from the notebook with the links
from the cloud? O
Ok, I am stopping now. Sorry.
But the bot cannot do the strip. It communicates with trac by using TAB as
separators. So any TAB in the field description breaks the channel..
Frederic
Le dimanche 6 septembre 2015 19:38:22 UTC+2, William a écrit :
>
> Frédéric -- please stop. I've received about
Frédéric -- please stop. I've received about 200 emails because of this,
at least. And as Nathann says, it doesn't make any sense...
On Sunday, September 6, 2015 at 10:29:12 AM UTC-7, Nathann Cohen wrote:
>
> P.S.: Frédéric: I just received my 10th email from trac because you
> removed a tab c
>
> Does anybody know why I'm getting hundreds (?) of email messages from
> trac today...? Is anybody else?
>
Yes. It's because Frederic is apparently removing all tabulations from the
descriptions of trac tickets.
Don't ask me.
https://groups.google.com/d/topic/sage-devel/IQqmxC8OW1k/discu
P.S.: Frédéric: I just received my 10th email from trac because you
removed a tab character from the description of "yet another" dead and
buried ticket.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop recei
Hi,
Does anybody know why I'm getting hundreds (?) of email messages from
trac today...? Is anybody else?
William
-- Forwarded message --
From: sage-trac
Date: Sun, Sep 6, 2015 at 10:19 AM
Subject: Re: [sage-trac] #7092: [with spkg, positive review] build
failure of pari-2.3.3
On Sunday, September 6, 2015 at 9:31:11 AM UTC-7, Nathann Cohen wrote:
>
> would it be possible to forbid the TAB character in the trac description
>> field, or to strip it somehow at user input ?
>>
>> The reason is that any TAB character will prevent the patchbot from
>> parsing correctly th
>
> would it be possible to forbid the TAB character in the trac description
> field, or to strip it somehow at user input ?
>
> The reason is that any TAB character will prevent the patchbot from
> parsing correctly the trac page. This then can have some funest
> consequences.
>
Tell me if I
On Sun, 6 Sep 2015, Michael Orlitzky wrote:
...and I see that this isn't happening any longer. But when most older
tickets were created, they were automatically assigned and left that way.
Well, I have made some tickets so that I have marked myself as an author.
For most, I have not.
Should
On 09/06/2015 09:46 AM, Michael Orlitzky wrote:
> On 09/06/2015 01:27 AM, Siddharth Bhat wrote:
>>
>> c) looked at the "for beginner" issues on Trac, but all of them seem to
>> have people assigned to them.
>>
>
> When a new ticket gets created, it automatically gets assigned to
> someone who migh
On 09/06/2015 01:27 AM, Siddharth Bhat wrote:
>
> c) looked at the "for beginner" issues on Trac, but all of them seem to
> have people assigned to them.
>
When a new ticket gets created, it automatically gets assigned to
someone who might be interested. That's mostly a relic from a time when
ce
Hello,
would it be possible to forbid the TAB character in the trac description
field, or to strip it somehow at user input ?
The reason is that any TAB character will prevent the patchbot from parsing
correctly the trac page. This then can have some funest consequences.
Frederic
--
You rec
Yo !
A developer is a user who blames the software when something goes wrong.
And who fixes the problem.
The best way to learn how the development process works is to first find
something in Sage that you want to fix/add. It can be a bug, it can be a
missing feature, it can be an u
On Sat, 5 Sep 2015, Siddharth Bhat wrote:
Are there issues that I can take up as a beginner? Could someone
"mentor" me for a while so I get the hang of sage's development process?
Review something. Here is a guide:
http://doc.sagemath.org/html/en/developer/reviewer_checklist.html#chapter-revi
Hey everyone :)
I've recently started using sage for graph theory and group theory. I'm a
programmer as well, so I was wondering how I could help out with Sage.
I have
a) built sage from source
b) created a Trac account
c) looked at the "for beginner" issues on Trac, but all of them seem to
hav
49 matches
Mail list logo
