Ran yapf on modular/abvar code

[klui]

I'm about to make changes to the modular/abvar code so I figure I ran yapf on it first.

[klui]

New commits:

​88bd3b3

ran yapf on abvar directory

[jdemeyer]

There are some strange formattings IMHO. For example

        if not self.is_subvariety_of_ambient_jacobian(
        ) or not other.is_subvariety_of_ambient_jacobian():

and

        elif isinstance(
                other,
                ModularAbelianVariety_abstract) and other.is_subvariety(self):

and

            decomp = [
                AbelianVariety(f) for f in self.newform_decomposition('a')
            ]

I'm not convinced that all of these are improvements.

[klui]

Okay, that's fair. I'll manually check it.

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​ef0bb6f

manually checked style

[klui]

I just manually checked it. I mostly changed how yapf handles long sequences of method application. I didn't like how it often ended a line with ( .

This one seems okay?

            decomp = [
                AbelianVariety(f) for f in self.newform_decomposition('a')
            ]

[jdemeyer]

This is of course bikeshedding, but I would write that like

            decomp = [AbelianVariety(f)
                      for f in self.newform_decomposition('a')]

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​84147ba

style change

[klui]

Replying to jdemeyer:

This is of course bikeshedding, but I would write that like

            decomp = [AbelianVariety(f)
                      for f in self.newform_decomposition('a')]

I like that too. Thanks!

[git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

​713c3b7	ran yapf on abvar directory
​30f79ad	manually checked style
​abf0185	style change

[embray]

Moving tickets from the Sage 8.8 milestone that have been actively worked on in the last six months to the next release milestone (optimistically).

[embray]

Ticket retargeted after milestone closed

[mkoeppe]

Batch modifying tickets that will likely not be ready for 9.1, based on a review of the ticket title, branch/review status, and last modification date.

[mkoeppe]

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

[mkoeppe]

Setting a new milestone for this ticket based on a cursory review.