| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Note that excluding in MANIFEST.in will exclude them from the sdist, which can make it hard for downstreams to test (if that matters). On what host were those /usr/local/lib/python2.7/dist-lib/ paths found? |
Sorry, something went wrong.
|
Ubuntu 14.04 |
Sorry, something went wrong.
|
@tseaver PTAL. I did a hacky thing my modifying sys.path in __main__. |
Sorry, something went wrong.
You mean we don't want those files to be there after they run sudo pip install gcloud? I'm thinking of downstream packagers, who might want to be able to run all the tests after creating a .deb/.rpm from the sdist. |
Sorry, something went wrong.
Yep. Is there a middle ground? |
Sorry, something went wrong.
|
I'm still against stripping the system tests from the sdist. Can we move the importable support code into a subpackage of gcloud, and just keep system_tests off the PYTHONPATH? |
Sorry, something went wrong.
|
Why do we want to ship our system tests? |
Sorry, something went wrong.
|
So that downstream packagers (e.g., .deb/.rpm) can run them to verify they have working code? |
Sorry, something went wrong.
|
Our system tests? These require a ton of set-up, including having to go to the Cloud Console and download a key. |
Sorry, something went wrong.
|
I've gotten feedback from .deb/.rpm maintainers in the past that they wanted to be able to verify the working state of the code they package by running tests afterward. Maybe they wouldn't run the system tests. OTOH, as the APIs change over time, asking users to run them to help debug configuration issues vs. software might be reasonable. |
Sorry, something went wrong.
|
It's not like git clone is difficult for the .deb/.rpm maintainers, or for users that are able to offer useful help |
Sorry, something went wrong.
|
@tseaver WDYT of my comment above? |
Sorry, something went wrong.
|
LGTM, on the basis that gcloud isn't the type of library we would expect to see as an OS-level dependency. Nor do I think it's a good idea to pursue that path, as it would hold our releases and support subject to OS release cycles (which are generally very slow). |
Sorry, something went wrong.
|
Filed #1451 for discussion of the possibility to ship the system tests as gcloud.system_tests. Merging for now. |
Sorry, something went wrong.
Excluding system tests from being installed.
These imports were broken by googleapis#1373.
Also removing system_tests/__init__.py so it is no longer a package and making all imports happen locally (rather than from the root of the project). Changes originally inspired by emulator script breakages in googleapis#1373.
Also removing system_tests/__init__.py so it is no longer a package and making all imports happen locally (rather than from the root of the project). Changes originally inspired by emulator script breakages in googleapis#1373.
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
* feat: support non vectorized managed function * fix mf tests * fix dataframe apply * fix series apply * fix the decorator in tests * fix test remote func * add more tests * remove unused import * refactor rf in bff session * del udf args * fix docstring * resolve the comments * fix the attribute naming * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md * resolve all comments * resolve comments * resolve comments * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md * fix lint * type ignore * resolve comments --------- Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
@tseaver I noticed this while trying to from system_tests import populate_datastore and the import failed due to reasons that were "resolved" in #1349.
Then I peaked and realized that the error was coming from
Notice that in our repo:
(This is due to the fact that system_tests/__init__.py was added in #954 / #273)