-
Notifications
You must be signed in to change notification settings - Fork 45
Conversation
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
noxfile.py
Outdated
@@ -139,7 +140,7 @@ def docs(session): | |||
"""Build the docs for this library.""" | |||
|
|||
session.install("-e", ".") | |||
session.install("sphinx", "alabaster", "recommonmark") | |||
session.install("sphinx<3.0", "alabaster", "recommonmark") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change has landed in synthtool but the library hasn't been updated
.gitignore
Outdated
@@ -28,7 +28,7 @@ pip-log.txt | |||
.nox | |||
.cache | |||
.pytest_cache | |||
|
|||
sponge_log.xml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the sponge_log.xml
generated by the sample tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing to consider is moving the samples into a project under the samples folder. This way, there can by multiple sample projects that are still different.
For example, you may want something like:
samples/snippets
samples/quickstart
samples/sample_app
Also, we may at some point wish to figure out how (and when) we want to test the content of the samples at HEAD for the client libraries - maybe a different session (or set of sessions)?
samples/noxfile.py
Outdated
@@ -0,0 +1,154 @@ | |||
# Copyright 2019 Google LLC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be 2020?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤔 This is a lightly edited version of noxfile-template.py
from python-docs-samples. I'm not sure what the policy is around copyright years in this case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you copy, keep the original date. If you want to add the new year, you'd better have multiple years.
Ah interesting. I see each project has its own I'll adjust the noxfile to parametrize the tests session if multiple sample project directories are found.
I edited the noxfile to install the library from HEAD, but you make a good point that it would be preferable to check both (latest published release and HEAD). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a handful of comments throughout but do have two meta concerns/comments
- Doug just did a fantastic job rewriting the authoring guide. How should we best link to that from client libraries?
- For every samples PR that is opened, we need to have a CL open to change all affected region tags in the docs
samples/README.rst
Outdated
@@ -0,0 +1,206 @@ | |||
.. This file is automatically generated. Do not edit this file directly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like previously folks could edit the readme directly in the samples - how will that work with this being autogenerated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have this problem with all the template files (noxfile.py, kokoro files). If someone submits a PR with an edit I ask them to make the change to the template source in synthtool.
If a change does sneak in, it'll be reverted in the next Autosynth PR.
My preference would be
So I have a slight preference to each project having it's own noxfile if possible. It makes it easier to copy and paste projects atomically, and avoid growing back into the monster shared noxfile we had before.
We also need to consider how this affects the docs. If we add a new feature (and update the samples) we need to make sure the samples on docs are frozen until the next release. |
How about I add a file
Do we need to configure something in google3 to make this happen? |
…rm/python-docs-samples#1538) * Added Audio Profile sample * Adjusted the row lengths * Adjusted the row length * Fixed Import orders * Fixed print statement * Debugging the unit test * Fixed the unit test * Some fixes per Noah's suggestions. * Renamed the function name in the test. * Multilined the long line. * Fixed the misspelling * Fixed the long line * Forcing the CicleCi to build again * Changing Inc to LLC * Updated library version. * Generated README.rst
…-samples#1586) * Printing the last paragraph only. * Python3 print * Removing sample rate setting * Adding the missing output parameter in the example * Changes based on the comments * Removed filenames as input parameters * Removed unused args * Updated README file * Updated the inline comment * Modified code to make it more readable * Simplified the response object processing. * Fixing the long line issue.
…loudPlatform/python-docs-samples#1738) * Get display name of enums using IntEnum Requires updating google-cloud-language to 1.1.0 * Add note about gs://demomaker for video test files * Get display name of enums using IntEnum * Get display name of enums using IntEnum * Revert "Add note about gs://demomaker for video test files" This reverts commit 39d9bfff03201f7c6dcb38fee3856dd537ab4b62.
…amples#1980) * Auto-update dependencies. * Update requirements.txt * Update requirements.txt
…CloudPlatform/python-docs-samples#2378) * fix: refactored MP3 file tests * fix: moving resources to cloud-client/resources * fix: removing expected_example.mp3
…-samples#2687) * Add voice selection by name * Add future to requirements.txt Fixes python2 test failures referencing html. Co-authored-by: Leah E. Cole <[email protected]>
…0)](GoogleCloudPlatform/python-docs-samples#3210) Co-authored-by: gcf-merge-on-green[bot] <60162190+gcf-merge-on-green[bot]@users.noreply.github.com>
…ples#2806) * chore(deps): update dependency requests to v2.23.0 * Simplify noxfile and add version control. * Configure appengine/standard to only test Python 2.7. * Update Kokokro configs to match noxfile. * Add requirements-test to each folder. * Remove Py2 versions from everything execept appengine/standard. * Remove conftest.py. * Remove appengine/standard/conftest.py * Remove 'no-sucess-flaky-report' from pytest.ini. * Add GAE SDK back to appengine/standard tests. * Fix typo. * Roll pytest to python 2 version. * Add a bunch of testing requirements. * Remove typo. * Add appengine lib directory back in. * Add some additional requirements. * Fix issue with flake8 args. * Even more requirements. * Readd appengine conftest.py. * Add a few more requirements. * Even more Appengine requirements. * Add webtest for appengine/standard/mailgun. * Add some additional requirements. * Add workaround for issue with mailjet-rest. * Add responses for appengine/standard/mailjet. Co-authored-by: Renovate Bot <[email protected]>
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
@@ -0,0 +1,66 @@ | |||
#!/usr/bin/env python |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to have copies of readme-gen everywhere? How do we maintain changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My pending synthtool PR adds readmegen into the synthtool. Eventually we can remove this separate script and only do sample README regens with the templates in synthtool.
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stamping this based on other approvals.
Pulls samples in from python-docs-samples along with the noxfile.