Skip to content

Conversation

@mattdangerw
Copy link
Member

Another round of style edits, and breakage fixes for docstrings.

With these changes, all our fenced docstrings now run across the repo! Though it does take 20 minutes on a fairly large machine.

Fixes #867
Fixes #641

@mattdangerw
Copy link
Member Author

/gcbrun

Copy link
Contributor

@jbischof jbischof left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

Ideally we would have an automated way to run our extra_large and docstring tests every day/week on GCP without having to worry about this on every PR.

@mattdangerw
Copy link
Member Author

Ideally we would have an automated way to run our extra_large and docstring tests every day/week on GCP without having to worry about this on every PR.

Fully agreed. A nightly testing routine would be a big help.

Another round of style edits, and breakage fixes for docstrings.

With these changes, all our fenced docstrings now run across the repo!
Though it does take 20 minutes on a fairly large machine.
@mattdangerw mattdangerw force-pushed the misc-docstring-fixes branch from b19b8bd to 6548c51 Compare April 20, 2023 00:05
@mattdangerw
Copy link
Member Author

/gcbrun

@mattdangerw mattdangerw merged commit 5b249c0 into keras-team:master Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rework model docstrings for progressive disclosure of complexity Remove phantom file references from fenced docstrings

2 participants