-
-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pycodestyle cleanup in strongly_regular_db.pyx (part 3) #34313
Comments
Branch: public/graphs/34313_part3 |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:3
You make many edits like this: - if (v == (q**d - 1)*((q**d)//(p**t) + 1)//(q - 1) and
- k == q*(q**(d-1) - 1)*((q**(d-1))//(p**t) + 1)//(q - 1) and
- l == q*q*(q**(d-2)-1)*((q**(d-2))//(p**t) + 1)//(q - 1) + q - 1):
+ if (v == (q**d - 1)*((q**d)//(p**t) + 1)//(q - 1) and
+ k == q*(q**(d-1) - 1)*((q**(d-1))//(p**t) + 1)//(q - 1) and
+ l == q*q*(q**(d-2)-1)*((q**(d-2))//(p**t) + 1)//(q - 1) + q - 1):
from sage.graphs.generators.classical_geometries import UnitaryPolarGraph I am not sure if this improves readability of the code. The change of the positions of Let's hear more opinions from others. |
comment:4
PEP8 allows for different conventions with how multiple lines of a conditional are done. I am not convinced that the original author intended for the |
comment:5
Okay then. |
Reviewer: Kwankyu Lee |
Changed branch from public/graphs/34313_part3 to |
We continue the cleaning of
strongly_regular_db.pyx
.This ticket is built on top of #34311 and #34312 to avoid conflicts.
Depends on #34311
Depends on #34312
CC: @fchapoton @tscrim
Component: graph theory
Author: David Coudert
Branch/Commit:
f2323c0
Reviewer: Kwankyu Lee
Issue created by migration from https://trac.sagemath.org/ticket/34313
The text was updated successfully, but these errors were encountered: