-
Notifications
You must be signed in to change notification settings - Fork 138
feat: Rename pybigquery to sqlalchemy-bigquery #198
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
feat: Rename pybigquery to sqlalchemy-bigquery #198
Conversation
It, itself isn't public.
and updated package name in copyright statement.
Could we add a warning to setup.py and the README and make a release of pybigquery first? I'd like to make sure folk who look for the pybigquery package are able to find sqlalchemy-bigquery. I'm thinking something similar to what we're doing here: https://pypi.org/project/google-cloud/ |
In this case, we'd be telling people to install a package that doesn't exist, wouldn't we? Note that pybigquery will continue to work indefinitely! Daft plan, modified based on your comment:
Thoughts @tswast ? |
True. Maybe we try to use some of the LTS client automation and keep around a |
There are a number of ways we could approach this, depending on what we
(you :) ) want to do. Let's discuss on Wednesday.
Jim
…On Tue, Jul 13, 2021 at 3:17 PM Tim Swast ***@***.***> wrote:
In this case, we'd be telling people to install a package that doesn't
exist, wouldn't we?
True. Maybe we try to use some of the LTS client automation and keep
around a pybigquery branch for backports? Or maybe we just manually
publish a release of pybigquery once sqlalchemy-bigquery is available?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#198 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF4U5YTOHRYENEPHAZOINTTXSGI3ANCNFSM47W3FT6A>
.
--
Jim Fulton
http://jimfulton.info
|
Co-authored-by: Tim Swast <swast@google.com>
Note that we have to sort out the new name, since the new name was taken. |
Hey @jimfulton and @tswast , I have added Jim as an owner on https://pypi.org/project/sqlalchemy_bigquery/ , and added a redirect notice on my old project at https://github.com/cpdean/sqlalchemy-bigquery . Let me know if there's anything else I can do to help. |
@cpdean Thank you very much! |
@tswast are you good with this? |
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.
Looking good! A couple minor comments. I think we can merge this sooner rather than later.
.repo-metadata.json
Outdated
"release_level": "beta", | ||
"language": "python", | ||
"library_type": "INTEGRATION", | ||
"repo": "googleapis/python-bigquery-sqlalchemy", | ||
"distribution_name": "pybigquery", | ||
"distribution_name": "sqlalchemy-bigquery" |
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.
Need extra comma now that we added api_id
"distribution_name": "sqlalchemy-bigquery" | |
"distribution_name": "sqlalchemy-bigquery", |
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.
Fixed
sqlalchemy_bigquery/__init__.py
Outdated
except ImportError: | ||
pass | ||
else: # pragma: NO COVER | ||
if not hasattr(pybigquery, "__version__"): |
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'm curious what the not hasattr
is doing. Could you add a comment about this? If __version__
is present it's less likely to conflict?
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.
That's a holdover from the shim, I think. The shim would have that attribute. I'll get rid of it.
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.
fixed
I also just removed the |
README.rst
Outdated
.. code-block:: python | ||
|
||
from pybigquery.api import ApiClient | ||
from sqlalchemy_bigquery.api import ApiClient | ||
api_client = ApiClient() | ||
print(api_client.dry_run_query(query=sqlstr).total_bytes_processed) |
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 can remove this code sample now that we don't have an ApiClient
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.
Dang, I did yesterday, but I guess that change lost in my docfx flailing. Thanks, will do.
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.
done
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #197 🦕