[sage-devel] Re: Git repository should have Sage versions as branches not tags

[Paul Masson]

Samuel, there are a couple pull requests from the middle of 2015 that never 
became Trac tickets. The bot appears to have stopped creating tickets 
before then.

There are open pull requests from the end of 2014 that became part of Sage 
6.4. The bot does not appear to close pull requests on GitHub.

The infrastructure wiki page lists Volker and Harald as the only admins for 
GitHub. Are there any others who could close the ten or so open items ready 
for closure in the Sage repository? If not, perhaps I'll bug Harald about 
it.

This may of course seem trivial to people, but if Sage is planning to move 
to GitHub in the future then then it makes sense to begin addressing GitHub 
maintenance more actively.


On Monday, July 18, 2016 at 1:12:31 AM UTC-7, Samuel Lelievre wrote:
>
> There is a bot (called sageb0t) that turns pull requests on GitHub into 
> trac tickets.
>
> It might be that the bot also closes pull requests when the corresponding 
> tickets
> have been closed on trac and a new public release of Sage happens (github 
> pull
> requests are typically against the master branch and public releases are 
> when
> this branch gets updated).
>
> The bot is maintained by Robert Bradshaw, he might be able to comment more.
> See https://wiki.sagemath.org/Infrastructure
>
>
> Le dimanche 17 juillet 2016 23:06:37 UTC+2, Paul Masson a écrit :
>>
>> Thanks.
>>
>> Another question: who closes Issues and Pull Requests on Github that have 
>> been marked ready for closure?
>>
>> On Sunday, July 17, 2016 at 1:56:38 AM UTC-7, Volker Braun wrote:
>>>
>>> done
>>>
>>> On Saturday, July 16, 2016 at 11:19:21 PM UTC+2, Paul Masson wrote:

 The mirror actually has three branches. This one hasn't been touched in 
 over a year:

 https://github.com/sagemath/sage/tree/module-list-cleanup

 Shouldn't it be removed at some point?

 On Wednesday, July 13, 2016 at 6:53:21 PM UTC-7, John Phamlore wrote:
>
> The mirror at
>
> https://github.com/sagemath/sage
>
> has only two branches, develop and master.  Versions seem to be kept 
> as tags.
>
> However, editing sage.yaml of binary-pkg
>
> https://github.com/sagemath/binary-pkg
>
> does not work for tags.
>


-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: sage -b fail

[leif]

Jeroen Demeyer wrote:
> On 2016-07-18 14:48, 'Paul Mercat' via sage-devel wrote:
>> But this command doesn't work even if I don't make any change in the
>> source code.
> 
> Note that changing git branches counts as changing source code. So
> I bet that you *did* make changes to the Sage source code since the last
> time you ran "make" successfully.
> 
> Anyway, when in doubt: run "make" (or "make build" to skip the
> documentation) instead of "sage -b".

Indeed, this was added with the last PARI update.  (I was really
wondering how he managed to get that error.)

git diff 6ef822df61a926d6be0fb7a420fed4d644641ef7
src/sage_setup/autogen/pari/doc.py
diff --git a/src/sage_setup/autogen/pari/doc.py
b/src/sage_setup/autogen/pari/doc.py
index def4efe..59e2635 100644
--- a/src/sage_setup/autogen/pari/doc.py
+++ b/src/sage_setup/autogen/pari/doc.py
@@ -107,6 +107,7 @@ def raw_to_rest(doc):
 doc = doc.replace("@[pm]", "±")
 doc = doc.replace("@[nbrk]", unichr(0xa0))
 doc = doc.replace("@[agrave]", "à")
+doc = doc.replace("@[aacute]", "á")
 doc = doc.replace("@[eacute]", "é")
 doc = doc.replace("@[ouml]", "ö")
 doc = doc.replace("@[uuml]", "ü")



-leif


-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage -b fail

[Jeroen Demeyer]

On 2016-07-18 14:48, 'Paul Mercat' via sage-devel wrote:

But this command doesn't work even if I don't make any change in the
source code.


Note that changing git branches counts as changing source code. So
I bet that you *did* make changes to the Sage source code since the last 
time you ran "make" successfully.


Anyway, when in doubt: run "make" (or "make build" to skip the 
documentation) instead of "sage -b".


--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: sage -b fail

[John Cremona]

On 18 July 2016 at 14:26, leif  wrote:
> John Cremona wrote:
>> I have a similar problem, on a machine which has successfully built
>> Sage in the past.  Version 7.2 (literally commit f76401f).
>>
>> The last few commainds in history are
>>
>> make distclean
>> ../configure
>> make
>> make
>>
>> but each of the last two make's ends with the following, also
>> mentioning sage_setup.autogen.pari:
>>
>>
>> make[3]: Entering directory `/home/lmfdb/sage/src'
>> python -c "from sage_setup.autogen.pari import rebuild; rebuild()"
>> sys:1: RuntimeWarning: not adding directory '' to sys.path since it's
>> writable by an untrusted group.
>> Untrusted users could put files in this directory which might then be
>> imported by your Python code. As a general precaution from similar
>> exploits, you should not execute Python code from this directory
>> Traceback (most recent call last):
>>   File "", line 1, in 
>> ImportError: No module named sage_setup.autogen.pari
>> make[3]: *** [sage/libs/pari/auto_gen.pxi] Error 1
>> make[3]: Leaving directory `/home/lmfdb/sage/src'
>
> Well, which group owns the folder, and does that group need write access?

Nothing unusual.  The directory and all under it are owned by the user
doing the build (me) and the group ownership is the same.  The
permissions are only for the user, not the group -- all this is
exactly as on all other machines where I build Sage often.

>
> As a work-around, either change the group or chmod g-w ...

OK -- I did a recursive g-w on the whole directory and that seems to
have done the trick.  I have no idea how the group access got to be so
lenient in this instance.

Now the build continues.

Thanks, Leif!

John

>
>
> -leif
>
>>
>> On 18 July 2016 at 14:04, Thierry  wrote:
>>> I can not reproduce your problem with 7.3.beta7 (downloaded from Sage's
>>> git/trac server).
>>>
>>> That said, if you make some modifications of Sage source code, you can just 
>>> do
>>> 'make' afterwards.
>>>
>>> Ciao,
>>> Thierry
>>>
>>>
>>> On Mon, Jul 18, 2016 at 05:48:39AM -0700, 'Paul Mercat' via sage-devel 
>>> wrote:
 Yes, I successfully ran 'make'.
 But I need to run 'sage -b' because I want to modify some things in the
 source code.
 But this command doesn't work even if I don't make any change in the source
 code.

 Ciao
 Paul

 Le lundi 18 juillet 2016 13:24:41 UTC+2, Thierry (sage-googlesucks@xxx) a
 écrit :
>
> Hi,
>
> On Mon, Jul 18, 2016 at 03:48:47AM -0700, 'Paul Mercat' via sage-devel
> wrote:
>> Hi !
>>
>> I just installed the last developpement version of sage with
>> git clone git://github.com/sagemath/sage.git
>> and it compiles correctly on my Ubuntu 16.04 computer.
>
> Do you mean that at this point you sucessfully ran 'make' ? If so, there
> is no
> need to run 'sage -b' (or you need to provide more details about your
> workflow).
>
> Ciao,
> Thierry
>
>
>> ... qflllTraceback (most recent call last):
>>   File "", line 1, in 
>>   File "sage_setup/autogen/pari/__init__.py", line 5, in rebuild
>> G()
>>   File "sage_setup/autogen/pari/generator.py", line 249, in __call__
>> self.handle_pari_function(**v)
>>   File "sage_setup/autogen/pari/generator.py", line 190, in
>> handle_pari_function
>> get_rest_doc(function))
>>   File "sage_setup/autogen/pari/doc.py", line 365, in get_rest_doc
>> return raw_to_rest(raw)
>>   File "sage_setup/autogen/pari/doc.py", line 224, in raw_to_rest
>> raise SyntaxError("@ found: " + doc[ilow:ihigh])
>> SyntaxError: @ found: i,j} <= \|0.51\|`, and the
>> Lov@[aacute]sz's constant is :mat
>> Makefile:19 : la recette pour la cible « sage/libs/pari/auto_gen.pxi » a
>> échouée
>> make: *** [sage/libs/pari/auto_gen.pxi] Erreur 1
>>
>> How can I get ride of this error ?
>> I really need to make this works in order to use tools that I have
>> developped for sage.
>>
>> Thanks !
>> Paul
>>
>> --
>> 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 https://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 

[sage-devel] Re: sage -b fail

[leif]

leif wrote:
> John Cremona wrote:
>> I have a similar problem, on a machine which has successfully built
>> Sage in the past.  Version 7.2 (literally commit f76401f).
>>
>> The last few commainds in history are
>>
>> make distclean
>> ../configure
>> make
>> make
>>
>> but each of the last two make's ends with the following, also
>> mentioning sage_setup.autogen.pari:
>>
>>
>> make[3]: Entering directory `/home/lmfdb/sage/src'
>> python -c "from sage_setup.autogen.pari import rebuild; rebuild()"
>> sys:1: RuntimeWarning: not adding directory '' to sys.path since it's
>> writable by an untrusted group.
>> Untrusted users could put files in this directory which might then be
>> imported by your Python code. As a general precaution from similar
>> exploits, you should not execute Python code from this directory
>> Traceback (most recent call last):
>>   File "", line 1, in 
>> ImportError: No module named sage_setup.autogen.pari
>> make[3]: *** [sage/libs/pari/auto_gen.pxi] Error 1
>> make[3]: Leaving directory `/home/lmfdb/sage/src'
> 
> Well, which group owns the folder, and does that group need write access?
> 
> As a work-around, either change the group or chmod g-w ...
> 
> 
> -leif


P.S.:  W.r.t. what Volker(?) considers an "untrusted group", see

build/pkgs/python2/patches/sys_path_security.patch


-leif


-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: sage -b fail

[leif]

John Cremona wrote:
> I have a similar problem, on a machine which has successfully built
> Sage in the past.  Version 7.2 (literally commit f76401f).
> 
> The last few commainds in history are
> 
> make distclean
> ../configure
> make
> make
> 
> but each of the last two make's ends with the following, also
> mentioning sage_setup.autogen.pari:
> 
> 
> make[3]: Entering directory `/home/lmfdb/sage/src'
> python -c "from sage_setup.autogen.pari import rebuild; rebuild()"
> sys:1: RuntimeWarning: not adding directory '' to sys.path since it's
> writable by an untrusted group.
> Untrusted users could put files in this directory which might then be
> imported by your Python code. As a general precaution from similar
> exploits, you should not execute Python code from this directory
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: No module named sage_setup.autogen.pari
> make[3]: *** [sage/libs/pari/auto_gen.pxi] Error 1
> make[3]: Leaving directory `/home/lmfdb/sage/src'

Well, which group owns the folder, and does that group need write access?

As a work-around, either change the group or chmod g-w ...


-leif

> 
> On 18 July 2016 at 14:04, Thierry  wrote:
>> I can not reproduce your problem with 7.3.beta7 (downloaded from Sage's
>> git/trac server).
>>
>> That said, if you make some modifications of Sage source code, you can just 
>> do
>> 'make' afterwards.
>>
>> Ciao,
>> Thierry
>>
>>
>> On Mon, Jul 18, 2016 at 05:48:39AM -0700, 'Paul Mercat' via sage-devel wrote:
>>> Yes, I successfully ran 'make'.
>>> But I need to run 'sage -b' because I want to modify some things in the
>>> source code.
>>> But this command doesn't work even if I don't make any change in the source
>>> code.
>>>
>>> Ciao
>>> Paul
>>>
>>> Le lundi 18 juillet 2016 13:24:41 UTC+2, Thierry (sage-googlesucks@xxx) a
>>> écrit :

 Hi,

 On Mon, Jul 18, 2016 at 03:48:47AM -0700, 'Paul Mercat' via sage-devel
 wrote:
> Hi !
>
> I just installed the last developpement version of sage with
> git clone git://github.com/sagemath/sage.git
> and it compiles correctly on my Ubuntu 16.04 computer.

 Do you mean that at this point you sucessfully ran 'make' ? If so, there
 is no
 need to run 'sage -b' (or you need to provide more details about your
 workflow).

 Ciao,
 Thierry


> ... qflllTraceback (most recent call last):
>   File "", line 1, in 
>   File "sage_setup/autogen/pari/__init__.py", line 5, in rebuild
> G()
>   File "sage_setup/autogen/pari/generator.py", line 249, in __call__
> self.handle_pari_function(**v)
>   File "sage_setup/autogen/pari/generator.py", line 190, in
> handle_pari_function
> get_rest_doc(function))
>   File "sage_setup/autogen/pari/doc.py", line 365, in get_rest_doc
> return raw_to_rest(raw)
>   File "sage_setup/autogen/pari/doc.py", line 224, in raw_to_rest
> raise SyntaxError("@ found: " + doc[ilow:ihigh])
> SyntaxError: @ found: i,j} <= \|0.51\|`, and the
> Lov@[aacute]sz's constant is :mat
> Makefile:19 : la recette pour la cible « sage/libs/pari/auto_gen.pxi » a
> échouée
> make: *** [sage/libs/pari/auto_gen.pxi] Erreur 1
>
> How can I get ride of this error ?
> I really need to make this works in order to use tools that I have
> developped for sage.
>
> Thanks !
> Paul
>
> --
> 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 https://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 https://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 https://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 

Re: [sage-devel] sage -b fail

[John Cremona]

I have a similar problem, on a machine which has successfully built
Sage in the past.  Version 7.2 (literally commit f76401f).

The last few commainds in history are

make distclean
./configure
make
make

but each of the last two make's ends with the following, also
mentioning sage_setup.autogen.pari:


make[3]: Entering directory `/home/lmfdb/sage/src'
python -c "from sage_setup.autogen.pari import rebuild; rebuild()"
sys:1: RuntimeWarning: not adding directory '' to sys.path since it's
writable by an untrusted group.
Untrusted users could put files in this directory which might then be
imported by your Python code. As a general precaution from similar
exploits, you should not execute Python code from this directory
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named sage_setup.autogen.pari
make[3]: *** [sage/libs/pari/auto_gen.pxi] Error 1
make[3]: Leaving directory `/home/lmfdb/sage/src'

On 18 July 2016 at 14:04, Thierry  wrote:
> I can not reproduce your problem with 7.3.beta7 (downloaded from Sage's
> git/trac server).
>
> That said, if you make some modifications of Sage source code, you can just do
> 'make' afterwards.
>
> Ciao,
> Thierry
>
>
> On Mon, Jul 18, 2016 at 05:48:39AM -0700, 'Paul Mercat' via sage-devel wrote:
>> Yes, I successfully ran 'make'.
>> But I need to run 'sage -b' because I want to modify some things in the
>> source code.
>> But this command doesn't work even if I don't make any change in the source
>> code.
>>
>> Ciao
>> Paul
>>
>> Le lundi 18 juillet 2016 13:24:41 UTC+2, Thierry (sage-googlesucks@xxx) a
>> écrit :
>> >
>> > Hi,
>> >
>> > On Mon, Jul 18, 2016 at 03:48:47AM -0700, 'Paul Mercat' via sage-devel
>> > wrote:
>> > > Hi !
>> > >
>> > > I just installed the last developpement version of sage with
>> > > git clone git://github.com/sagemath/sage.git
>> > > and it compiles correctly on my Ubuntu 16.04 computer.
>> >
>> > Do you mean that at this point you sucessfully ran 'make' ? If so, there
>> > is no
>> > need to run 'sage -b' (or you need to provide more details about your
>> > workflow).
>> >
>> > Ciao,
>> > Thierry
>> >
>> >
>> > > ... qflllTraceback (most recent call last):
>> > >   File "", line 1, in 
>> > >   File "sage_setup/autogen/pari/__init__.py", line 5, in rebuild
>> > > G()
>> > >   File "sage_setup/autogen/pari/generator.py", line 249, in __call__
>> > > self.handle_pari_function(**v)
>> > >   File "sage_setup/autogen/pari/generator.py", line 190, in
>> > > handle_pari_function
>> > > get_rest_doc(function))
>> > >   File "sage_setup/autogen/pari/doc.py", line 365, in get_rest_doc
>> > > return raw_to_rest(raw)
>> > >   File "sage_setup/autogen/pari/doc.py", line 224, in raw_to_rest
>> > > raise SyntaxError("@ found: " + doc[ilow:ihigh])
>> > > SyntaxError: @ found: i,j} <= \|0.51\|`, and the
>> > > Lov@[aacute]sz's constant is :mat
>> > > Makefile:19 : la recette pour la cible « sage/libs/pari/auto_gen.pxi » a
>> > > échouée
>> > > make: *** [sage/libs/pari/auto_gen.pxi] Erreur 1
>> > >
>> > > How can I get ride of this error ?
>> > > I really need to make this works in order to use tools that I have
>> > > developped for sage.
>> > >
>> > > Thanks !
>> > > Paul
>> > >
>> > > --
>> > > 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 https://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 https://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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit 

Re: [sage-devel] sage -b fail

[Thierry]

I can not reproduce your problem with 7.3.beta7 (downloaded from Sage's
git/trac server).

That said, if you make some modifications of Sage source code, you can just do
'make' afterwards.

Ciao,
Thierry


On Mon, Jul 18, 2016 at 05:48:39AM -0700, 'Paul Mercat' via sage-devel wrote:
> Yes, I successfully ran 'make'.
> But I need to run 'sage -b' because I want to modify some things in the 
> source code.
> But this command doesn't work even if I don't make any change in the source 
> code.
> 
> Ciao
> Paul
> 
> Le lundi 18 juillet 2016 13:24:41 UTC+2, Thierry (sage-googlesucks@xxx) a 
> écrit :
> >
> > Hi, 
> >
> > On Mon, Jul 18, 2016 at 03:48:47AM -0700, 'Paul Mercat' via sage-devel 
> > wrote: 
> > > Hi ! 
> > > 
> > > I just installed the last developpement version of sage with 
> > > git clone git://github.com/sagemath/sage.git 
> > > and it compiles correctly on my Ubuntu 16.04 computer. 
> >
> > Do you mean that at this point you sucessfully ran 'make' ? If so, there 
> > is no 
> > need to run 'sage -b' (or you need to provide more details about your 
> > workflow). 
> >
> > Ciao, 
> > Thierry 
> >
> >
> > > ... qflllTraceback (most recent call last): 
> > >   File "", line 1, in  
> > >   File "sage_setup/autogen/pari/__init__.py", line 5, in rebuild 
> > > G() 
> > >   File "sage_setup/autogen/pari/generator.py", line 249, in __call__ 
> > > self.handle_pari_function(**v) 
> > >   File "sage_setup/autogen/pari/generator.py", line 190, in 
> > > handle_pari_function 
> > > get_rest_doc(function)) 
> > >   File "sage_setup/autogen/pari/doc.py", line 365, in get_rest_doc 
> > > return raw_to_rest(raw) 
> > >   File "sage_setup/autogen/pari/doc.py", line 224, in raw_to_rest 
> > > raise SyntaxError("@ found: " + doc[ilow:ihigh]) 
> > > SyntaxError: @ found: i,j} <= \|0.51\|`, and the 
> > > Lov@[aacute]sz's constant is :mat 
> > > Makefile:19 : la recette pour la cible « sage/libs/pari/auto_gen.pxi » a 
> > > échouée 
> > > make: *** [sage/libs/pari/auto_gen.pxi] Erreur 1 
> > > 
> > > How can I get ride of this error ? 
> > > I really need to make this works in order to use tools that I have 
> > > developped for sage. 
> > > 
> > > Thanks ! 
> > > Paul 
> > > 
> > > -- 
> > > 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 https://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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

[Erik Bray]

On Mon, Jul 18, 2016 at 12:46 PM, Thierry
 wrote:
> Hi,
>
> On Mon, Jul 18, 2016 at 12:17:48PM +0200, Erik Bray wrote:
> [...]
>> Additionally, I think we should allow issues (without code) to be
>> posted on GitHub, and have an easy way to convert a GitHub issue to a
>> Trac ticket.  I don't think it should be done for all issues, but
>> rather use GitHub as the "user-facing" issue tracker, while Trac is
>> the developer-facing issue tracker.  So a one-click way to make a Trac
>> ticket from a GitHub issue could be useful.
>
> Why not. Though it will require some human work to select and incorporate 
> valid
> issues for the long term and in a regular basis. This is the main problem that
> has to be solved, beyond writing an interface. Indeed, we used to have a 
> google
> spreadsheet to report bugs, that was just rotting, see e.g.
> https://groups.google.com/forum/?fromgroups#!searchin/sage-devel/google$20bug$20report/sage-devel/FvxgKfI9CZU/MhfiZBJQJ3IJ
> https://groups.google.com/forum/?fromgroups#!searchin/sage-devel/google$20bug$20report/sage-devel/EX4OYOlZqPI/meYYOuV-GXEJ
>
> Note that ask also plays a role of bug reporting, see the confirmed_bug and
> fixed_bug tags:
>
> http://ask.sagemath.org/questions/scope:all/sort:activity-desc/tags:confirmed_bug/page:1/
> http://ask.sagemath.org/questions/scope:all/sort:activity-desc/tags:fixed_bug/page:1/
>
> It is unfortunately absolutely not automated, but it works pretty well, due to
> the fact that some developers get connected frequently.

Right, there's little hope of automating such a thing.  Some people
have to actually check the issue reports on GH and review them.  Many
will probably tend to be duplicates which can be closed quickly.

I would just see it as an extension of the bug reports that come
through sage-devel.  If it were me, I'd be filtering them all into one
bucket.  Others, if  they find GH issues to add too much noise, can
ignore/unsubscribe from them.

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage -b fail

['Paul Mercat' via sage-devel]

Yes, I successfully ran 'make'.
But I need to run 'sage -b' because I want to modify some things in the 
source code.
But this command doesn't work even if I don't make any change in the source 
code.

Ciao
Paul

Le lundi 18 juillet 2016 13:24:41 UTC+2, Thierry (sage-googlesucks@xxx) a 
écrit :
>
> Hi, 
>
> On Mon, Jul 18, 2016 at 03:48:47AM -0700, 'Paul Mercat' via sage-devel 
> wrote: 
> > Hi ! 
> > 
> > I just installed the last developpement version of sage with 
> > git clone git://github.com/sagemath/sage.git 
> > and it compiles correctly on my Ubuntu 16.04 computer. 
>
> Do you mean that at this point you sucessfully ran 'make' ? If so, there 
> is no 
> need to run 'sage -b' (or you need to provide more details about your 
> workflow). 
>
> Ciao, 
> Thierry 
>
>
> > ... qflllTraceback (most recent call last): 
> >   File "", line 1, in  
> >   File "sage_setup/autogen/pari/__init__.py", line 5, in rebuild 
> > G() 
> >   File "sage_setup/autogen/pari/generator.py", line 249, in __call__ 
> > self.handle_pari_function(**v) 
> >   File "sage_setup/autogen/pari/generator.py", line 190, in 
> > handle_pari_function 
> > get_rest_doc(function)) 
> >   File "sage_setup/autogen/pari/doc.py", line 365, in get_rest_doc 
> > return raw_to_rest(raw) 
> >   File "sage_setup/autogen/pari/doc.py", line 224, in raw_to_rest 
> > raise SyntaxError("@ found: " + doc[ilow:ihigh]) 
> > SyntaxError: @ found: i,j} <= \|0.51\|`, and the 
> > Lov@[aacute]sz's constant is :mat 
> > Makefile:19 : la recette pour la cible « sage/libs/pari/auto_gen.pxi » a 
> > échouée 
> > make: *** [sage/libs/pari/auto_gen.pxi] Erreur 1 
> > 
> > How can I get ride of this error ? 
> > I really need to make this works in order to use tools that I have 
> > developped for sage. 
> > 
> > Thanks ! 
> > Paul 
> > 
> > -- 
> > 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage -b fail

[Thierry]

Hi,

On Mon, Jul 18, 2016 at 03:48:47AM -0700, 'Paul Mercat' via sage-devel wrote:
> Hi !
> 
> I just installed the last developpement version of sage with
> git clone git://github.com/sagemath/sage.git
> and it compiles correctly on my Ubuntu 16.04 computer.

Do you mean that at this point you sucessfully ran 'make' ? If so, there is no
need to run 'sage -b' (or you need to provide more details about your
workflow).

Ciao,
Thierry


> ... qflllTraceback (most recent call last):
>   File "", line 1, in 
>   File "sage_setup/autogen/pari/__init__.py", line 5, in rebuild
> G()
>   File "sage_setup/autogen/pari/generator.py", line 249, in __call__
> self.handle_pari_function(**v)
>   File "sage_setup/autogen/pari/generator.py", line 190, in 
> handle_pari_function
> get_rest_doc(function))
>   File "sage_setup/autogen/pari/doc.py", line 365, in get_rest_doc
> return raw_to_rest(raw)
>   File "sage_setup/autogen/pari/doc.py", line 224, in raw_to_rest
> raise SyntaxError("@ found: " + doc[ilow:ihigh])
> SyntaxError: @ found: i,j} <= \|0.51\|`, and the
> Lov@[aacute]sz's constant is :mat
> Makefile:19 : la recette pour la cible « sage/libs/pari/auto_gen.pxi » a 
> échouée
> make: *** [sage/libs/pari/auto_gen.pxi] Erreur 1
> 
> How can I get ride of this error ?
> I really need to make this works in order to use tools that I have 
> developped for sage.
> 
> Thanks !
> Paul
> 
> -- 
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

[Thierry]

Hi,

On Mon, Jul 18, 2016 at 12:17:48PM +0200, Erik Bray wrote:
[...]
> Additionally, I think we should allow issues (without code) to be
> posted on GitHub, and have an easy way to convert a GitHub issue to a
> Trac ticket.  I don't think it should be done for all issues, but
> rather use GitHub as the "user-facing" issue tracker, while Trac is
> the developer-facing issue tracker.  So a one-click way to make a Trac
> ticket from a GitHub issue could be useful.

Why not. Though it will require some human work to select and incorporate valid
issues for the long term and in a regular basis. This is the main problem that
has to be solved, beyond writing an interface. Indeed, we used to have a google
spreadsheet to report bugs, that was just rotting, see e.g.
https://groups.google.com/forum/?fromgroups#!searchin/sage-devel/google$20bug$20report/sage-devel/FvxgKfI9CZU/MhfiZBJQJ3IJ
https://groups.google.com/forum/?fromgroups#!searchin/sage-devel/google$20bug$20report/sage-devel/EX4OYOlZqPI/meYYOuV-GXEJ

Note that ask also plays a role of bug reporting, see the confirmed_bug and
fixed_bug tags:

http://ask.sagemath.org/questions/scope:all/sort:activity-desc/tags:confirmed_bug/page:1/
http://ask.sagemath.org/questions/scope:all/sort:activity-desc/tags:fixed_bug/page:1/

It is unfortunately absolutely not automated, but it works pretty well, due to
the fact that some developers get connected frequently.

Ciao,
Thierry

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] sage -b fail

['Paul Mercat' via sage-devel]

Hi !

I just installed the last developpement version of sage with
git clone git://github.com/sagemath/sage.git
and it compiles correctly on my Ubuntu 16.04 computer.
But after that the command "./sage -b" fail with the following error :

... qflllTraceback (most recent call last):
  File "", line 1, in 
  File "sage_setup/autogen/pari/__init__.py", line 5, in rebuild
G()
  File "sage_setup/autogen/pari/generator.py", line 249, in __call__
self.handle_pari_function(**v)
  File "sage_setup/autogen/pari/generator.py", line 190, in 
handle_pari_function
get_rest_doc(function))
  File "sage_setup/autogen/pari/doc.py", line 365, in get_rest_doc
return raw_to_rest(raw)
  File "sage_setup/autogen/pari/doc.py", line 224, in raw_to_rest
raise SyntaxError("@ found: " + doc[ilow:ihigh])
SyntaxError: @ found: i,j} <= \|0.51\|`, and the
Lov@[aacute]sz's constant is :mat
Makefile:19 : la recette pour la cible « sage/libs/pari/auto_gen.pxi » a 
échouée
make: *** [sage/libs/pari/auto_gen.pxi] Erreur 1

How can I get ride of this error ?
I really need to make this works in order to use tools that I have 
developped for sage.

Thanks !
Paul

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

[Erik Bray]

On Mon, Jul 18, 2016 at 10:12 AM, Samuel Lelievre
 wrote:
> There is a bot (called sageb0t) that turns pull requests on GitHub into trac
> tickets.
>
> It might be that the bot also closes pull requests when the corresponding
> tickets
> have been closed on trac and a new public release of Sage happens (github
> pull
> requests are typically against the master branch and public releases are
> when
> this branch gets updated).
>
> The bot is maintained by Robert Bradshaw, he might be able to comment more.
> See https://wiki.sagemath.org/Infrastructure

Oh, I didn't know that!  I was just thinking the other day that we
should have such a thing.  Good to see it's already done.

Additionally, I think we should allow issues (without code) to be
posted on GitHub, and have an easy way to convert a GitHub issue to a
Trac ticket.  I don't think it should be done for all issues, but
rather use GitHub as the "user-facing" issue tracker, while Trac is
the developer-facing issue tracker.  So a one-click way to make a Trac
ticket from a GitHub issue could be useful.

> Le dimanche 17 juillet 2016 23:06:37 UTC+2, Paul Masson a écrit :
>>
>> Thanks.
>>
>> Another question: who closes Issues and Pull Requests on Github that have
>> been marked ready for closure?
>>
>> On Sunday, July 17, 2016 at 1:56:38 AM UTC-7, Volker Braun wrote:
>>>
>>> done
>>>
>>> On Saturday, July 16, 2016 at 11:19:21 PM UTC+2, Paul Masson wrote:

 The mirror actually has three branches. This one hasn't been touched in
 over a year:

 https://github.com/sagemath/sage/tree/module-list-cleanup

 Shouldn't it be removed at some point?

 On Wednesday, July 13, 2016 at 6:53:21 PM UTC-7, John Phamlore wrote:
>
> The mirror at
>
> https://github.com/sagemath/sage
>
> has only two branches, develop and master.  Versions seem to be kept as
> tags.
>
> However, editing sage.yaml of binary-pkg
>
> https://github.com/sagemath/binary-pkg
>
> does not work for tags.
>
> --
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Indicate hidden output in Sage worksheet

[Art Vandelay]

Hello,

the output in a Sage worksheet can be hidden.

   - *Hide/Show Output:* Click on the left side of output to toggle between 
   hidden, shown with word wrap, and shown without word wrap.

It is however not indicated in which state the output sell currently is. I 
repeatedly ran into the problem that after expanding the stack trace of an 
error I unintentionally left the output cell in a state that hid part of 
the output and I didn't realize what was going on. I searched for an error 
in the code, restarted the worksheet, etc.


It would be great to see an indicator if some output is hidden.


Best regards!

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Git repository should have Sage versions as branches not tags

[Samuel Lelievre]

There is a bot (called sageb0t) that turns pull requests on GitHub into 
trac tickets.

It might be that the bot also closes pull requests when the corresponding 
tickets
have been closed on trac and a new public release of Sage happens (github 
pull
requests are typically against the master branch and public releases are 
when
this branch gets updated).

The bot is maintained by Robert Bradshaw, he might be able to comment more.
See https://wiki.sagemath.org/Infrastructure


Le dimanche 17 juillet 2016 23:06:37 UTC+2, Paul Masson a écrit :
>
> Thanks.
>
> Another question: who closes Issues and Pull Requests on Github that have 
> been marked ready for closure?
>
> On Sunday, July 17, 2016 at 1:56:38 AM UTC-7, Volker Braun wrote:
>>
>> done
>>
>> On Saturday, July 16, 2016 at 11:19:21 PM UTC+2, Paul Masson wrote:
>>>
>>> The mirror actually has three branches. This one hasn't been touched in 
>>> over a year:
>>>
>>> https://github.com/sagemath/sage/tree/module-list-cleanup
>>>
>>> Shouldn't it be removed at some point?
>>>
>>> On Wednesday, July 13, 2016 at 6:53:21 PM UTC-7, John Phamlore wrote:

 The mirror at

 https://github.com/sagemath/sage

 has only two branches, develop and master.  Versions seem to be kept as 
 tags.

 However, editing sage.yaml of binary-pkg

 https://github.com/sagemath/binary-pkg

 does not work for tags.

>>>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.