Re: [sage-devel] zenodo (DOI) for Sage releases is back!

[Dima Pasechnik]

On Tue, Oct 6, 2020 at 9:53 PM François Bissey  wrote:
>
> That’s nice but it looks like there could be improvement to the authors’ list.
> Some people appear by handle rather than name. Is it because they don’t give 
> their real
> names on GitHub?

yes, people who are listed by their github handles are ones who don't
have "real" full names on GitHub.

As far as truncation of the list goes, it seems they always stop at 30 names.

Not sure how to fix this, hopefully it is possible.

> Or don’t have a GitHub account? It also looks truncated.
>
> > On 7/10/2020, at 9:46 AM, Dima Pasechnik  wrote:
> >
> > We've recovered the settings for getting DOI for Sage releases via
> > zenodo, something that was broken for years.
> > cf https://zenodo.org/record/4066866
> > and this is DOI for Sage 9.1: https://doi.org/10.5281/zenodo.4066866
> >
> > --
> > 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 view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-devel/CAAWYfq1%2BmY1uULNUsEXwOk8rVyYVJ0%3DxJ9EoRp2naDFz7o99xg%40mail.gmail.com.
>
> --
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/54FC8789-0BA0-4CC6-A273-34E55CB94785%40gmail.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq21rh_uJCmRNrcjZEmgAhX5zD1T_RkKJo-p7TrCWVv%2Bmg%40mail.gmail.com.

Re: [sage-devel] zenodo (DOI) for Sage releases is back!

[François Bissey]

That’s nice but it looks like there could be improvement to the authors’ list.
Some people appear by handle rather than name. Is it because they don’t give 
their real
names on GitHub? Or don’t have a GitHub account? It also looks truncated.

> On 7/10/2020, at 9:46 AM, Dima Pasechnik  wrote:
> 
> We've recovered the settings for getting DOI for Sage releases via
> zenodo, something that was broken for years.
> cf https://zenodo.org/record/4066866
> and this is DOI for Sage 9.1: https://doi.org/10.5281/zenodo.4066866
> 
> -- 
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq1%2BmY1uULNUsEXwOk8rVyYVJ0%3DxJ9EoRp2naDFz7o99xg%40mail.gmail.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/54FC8789-0BA0-4CC6-A273-34E55CB94785%40gmail.com.

[sage-devel] zenodo (DOI) for Sage releases is back!

[Dima Pasechnik]

We've recovered the settings for getting DOI for Sage releases via
zenodo, something that was broken for years.
cf https://zenodo.org/record/4066866
and this is DOI for Sage 9.1: https://doi.org/10.5281/zenodo.4066866

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq1%2BmY1uULNUsEXwOk8rVyYVJ0%3DxJ9EoRp2naDFz7o99xg%40mail.gmail.com.

[sage-devel] Re: Proposal to add "tox" as a standard package - entry point for testing and linting

[Matthias Koeppe]

On Tuesday, October 6, 2020 at 7:34:41 AM UTC-7, jplab wrote:
>
> This looks like a great new feature! I discovered it by surprise when the 
> command "pep8 -v some_file.py" was not returning anything anymore, while 
> typically it returns hundreds of lines...
>
> Looking a bit around, I guess that one should add a few of the typical 
> PEP8 errors in tox.ini? Does that make sense? It seems that the lines 
> responsible for that are:
>
> [pycodestyle] 
>   
>
>
> # Check for the following issues:
> # E401: multiple imports on one line
> # E701: multiple statements on one line (colon)
> # E702: multiple statements on one line (semicolon)
> # W605: invalid escape sequence ‘x’
> # See https://pycodestyle.pycqa.org/en/latest/intro.html#error-codes
> select = E401,E701,E702,W605
> max-line-length = 160
>
> I'm thinking about the usual "Empty line contains whitespaces", and 
> similar... should they all be listed here?
>
> If I understood correctly, this likely affects everyone using pep8 while 
> coding and linting... What should be the Sage-9.2-method/command to get 
> something that looks like the good old "pep8 -v" output?
>

The configuration set in tox.ini is the same as the one used by the 
patchbot.

The command

./sage --tox -e pycodestyle -- --help

shows the options available for pycodestyle. (Note "--", to separate from 
tox options.) For example, you could use:

./sage --tox -v -e pycodestyle -- 
--select=E121,E123,E126,E226,E24,E704,W503,W504 src/sage/geometry

If we wanted, we could add a variant (perhaps called "./sage --tox -e 
pycodestyle-strict") that activates a stricter set of options than what the 
patchbot uses.




 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0af204d8-81bb-411c-8049-03eb6471c8bao%40googlegroups.com.

[sage-devel] Re: Proposal to add "tox" as a standard package - entry point for testing and linting

[jplab]

Hi!

This looks like a great new feature! I discovered it by surprise when the 
command "pep8 -v some_file.py" was not returning anything anymore, while 
typically it returns hundreds of lines...

Looking a bit around, I guess that one should add a few of the typical PEP8 
errors in tox.ini? Does that make sense? It seems that the lines 
responsible for that are:

[pycodestyle]   

   

# Check for the following issues:
# E401: multiple imports on one line
# E701: multiple statements on one line (colon)
# E702: multiple statements on one line (semicolon)
# W605: invalid escape sequence ‘x’
# See https://pycodestyle.pycqa.org/en/latest/intro.html#error-codes
select = E401,E701,E702,W605
max-line-length = 160

I'm thinking about the usual "Empty line contains whitespaces", and 
similar... should they all be listed here?

If I understood correctly, this likely affects everyone using pep8 while 
coding and linting... What should be the Sage-9.2-method/command to get 
something that looks like the good old "pep8 -v" output?

Le mercredi 9 septembre 2020 à 19:05:44 UTC+2, Matthias Koeppe a écrit :

> On Monday, September 7, 2020 at 2:18:34 PM UTC-7, Matthias Koeppe wrote:
>
>> tox (https://tox.readthedocs.io/en/latest/) is a popular package that is 
>> used by a large number of Python projects as the standard entry point for 
>> testing and linting.
>>
> [...] 
>>
> I propose to make "tox" a standard package of the Sage distribution so 
>> that this functionality becomes available by default.
>>
>> By convention, this requires a vote here on sage-devel.
>>
>>
> Thanks everyone. This is now https://trac.sagemath.org/ticket/30416 
> , needs review
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cb70c071-974d-4727-97f7-e0334f4d3ef5n%40googlegroups.com.