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

2020-10-06 Thread 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 handl

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

2020-10-06 Thread 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: > >

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

2020-10-06 Thread 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] Re: Proposal to add "tox" as a standard package - entry point for testing and linting

2020-10-06 Thread 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

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

2020-10-06 Thread 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 t