[sage-devel] Re: Question about Ubuntu patchbot

[Frédéric Chapoton]

If you are talking about the patchbot named

Ubuntu/18.4/x86_64/3.13.0-170-generic/44e979ad077a 

then it is known to be a rather problematic one. We do not know who is 
running this patchbot. It has therefore several problems that have not been 
fixed despite being known for at least 6 months. Patchbot owners are 
supposed to provide their trac name in the patchbot config, but here 
somebody didn't.

F

Le mercredi 10 juillet 2019 00:03:07 UTC+2, Paul Masson a écrit :
>
> In the process of reviewing https://trac.sagemath.org/ticket/28130, I 
> noticed that the Ubuntu patchbot fails to apply the commits of this ticket 
> to 8.9.beta1. I created a clean branch of 8.9.beta1 and successfully merged 
> the commits of this ticket without any issues, so what's up with the 
> patchbot? Is this a real build error or a patchbot error?
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cc9cefce-a3b9-4791-8a25-b9ed1b6442d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: New contributor experience

[Jerry James]

On Sunday, July 7, 2019 at 4:47:13 AM UTC-6, vdelecroix wrote:
>
> If you succeed in packaging for Fedora, the SageMath installation 
> guide should be updated accordingly. More precisely the two pages 
>
> https://doc.sagemath.org/html/en/installation/index.html 
> 
>  
> https://doc.sagemath.org/html/en/installation/linux.html 
>
 
Actually, we do have sagemath in Fedora already.  There have been some 
issues with it, but we've been working to clean those up and give our users 
a good experience.  One issue, for example, is that Fedora started removing 
python 2 around the end of 2018.  So many packages that sagemath needs were 
removed that we were left with no choice but to switch to python 3 for 
Fedora 30.  That's been a little rough, but it is getting better with every 
sagemath release.  We appreciate all the work the sagemath community has 
been doing to make that transition happen.

I'm not sure how to contribute text to the two pages you mentioned.  There 
has been a sagemath package in some form or other since Fedora 18, so 
perhaps "Fedora >= 18" could be added 
to https://doc.sagemath.org/html/en/installation/index.html?

As for https://doc.sagemath.org/html/en/installation/linux.html, the 
command "sudo dnf install sagemath" will install almost everything.  For 
some reason it leaves out the notebook exporter; that should perhaps be 
considered a bug.  The command "sudo dnf install sagemath-notebook-export" 
will install that.  The English documentation (sagemath-doc-en) is 
installed by default.  Documentation for other languages can be installed 
with "sudo dnf install sagemath-doc-XX" for suitable values of XX (ca, de, 
fr, hu, it, pt, ru, and tr).

Regards,
Jerry James

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b7d5a2ae-c4cf-4e3b-9e6c-8cbd8875b3ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Question about Ubuntu patchbot

[Paul Masson]

In the process of reviewing https://trac.sagemath.org/ticket/28130, I 
noticed that the Ubuntu patchbot fails to apply the commits of this ticket 
to 8.9.beta1. I created a clean branch of 8.9.beta1 and successfully merged 
the commits of this ticket without any issues, so what's up with the 
patchbot? Is this a real build error or a patchbot error?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/110878b9-d314-4fa5-8671-ed0626054598%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: How do you close a trac ticket?

[Simon King]

Hi Isuru,

On 2019-07-09, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> The usual procedure is to set the milestone to "won't fix/duplicate" and
> then "needs review".

To elaborate a bit more (because in the past at some point I had the
same problem):

A ticket can only be *closed* by someone with particular privileges on
trac, such as the release manager. Other users can only *suggest* a
particular resolution of a ticket.

Therefore the milestone should be set as Vincent said. But in addition
to that, the ticket shouldn't just be set to "needs review", but someone
(perhaps you) should indicate in a comment why this ticket is a
duplicate ("This is a duplicate of #1."), should insert his/her name
into the "Reviewer" field, and change the ticket to "positive review".

If I understand correctly, the release manager will look at the tickets
with positive review and take action on them (either merging them or
closing them or pointing out problems that the reviewer didn't notice,
etc.)

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 https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/qg2qu0%249mj%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Gap pexpect error when most Gap packages are installed

[Dima Pasechnik]

by the way, could please someone review 
https://trac.sagemath.org/ticket/28088
(update to GAP 4.10.2)


On Sunday, June 23, 2019 at 6:24:09 PM UTC+2, Antonio Rojas wrote:
>
> I just noticed this yesterday after updating GAP to 4.10.2 in Arch. 
> SymmetricGroup(n).conjugacy_classes_subgroups() works fine for n<=4, and 
> fails for n>=5. Same as you, it works after removing all additional GAP 
> packages.
>
> Additionally, after the update (and with all GAP packages installed) some 
> tests started failing due to using more memory than the default 330 
> maximum. Running them with -m0 makes them pass. Again, no issue if I remove 
> the additional packages. 
>
> El domingo, 23 de junio de 2019, 16:25:45 (UTC+2), Isuru Fernando escribió:
>>
>> In the conda package for gap, we packaged almost all of the gap packages 
>> (136 of 145) and sage pexpect gives an error for the following,
>>
>> sage: SymmetricGroup(7).conjugacy_classes_subgroups()
>>
>> saying,
>> RuntimeError: Gap produced error output
>> Error, sorry, the GAP Tables Of Marks Library is not installed
>>
>> I checked gap separately and tomlib imports fine and also running the 
>> equivalent command on gap runs fine. When I run the command in gap with the 
>> sage created workspace I get the same issue.
>>
>> I removed all gap packages except for the 18 packages that sage installs, 
>> cleared the cache and it works. So, this is clearly an issue with a package 
>> that sage doesn't install.
>>
>> Has anyone seen such an error before?
>>
>> Isuru
>>
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c2f13a01-aa2d-4484-9e86-18875abb8fc5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] doctest a single function or class

[TB]

Dear list,

Is there a way to test a single docstring of a function/method, or all 
the docstrings in a specific class, and not an entire module?


This is useful when testing a long file, without copying the needed 
docstring to a new file. This is also different than 
TestSuite(obj).run(). Currently I could only find the run_doctests() 
functions that accepts modules, but not objects. Should I open a ticket 
to add support for objects, or a flag to the TestSuite to run the 
doctest (but not recursively)?


The command-line interface of the built-in unittest module in Python 
supports this usecase:

$ python -m unittest test_module.TestClass.test_method
to test a specific method.

Regards,
TB

[1] https://docs.python.org/3/library/unittest.html#command-line-interface

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/860150ce-8abe-d000-539d-0099b74bef73%40gmail.com.
For more options, visit https://groups.google.com/d/optout.