-
Notifications
You must be signed in to change notification settings - Fork 148
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
Rename package to sqlalchemy_redshift #58
Conversation
ae87d75
to
c712dd3
Compare
) | ||
|
||
# All references to module redshift_sqlalchemy will map to sqlalchemy_redshift | ||
sys.modules['redshift_sqlalchemy'] = sqlalchemy_redshift |
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 just discovered sys.modules
. This appears to do the magic that we want. It's possible to do imports like from redshift_sqlalchemy.dialect import RedshiftDDLCompiler
.
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 correct but according to the six.py source code this method breaks:
from redshift_sqlalchemy import dialect
reload(dialect)
but I don't mind.
Can you add a deprecation warning to this module?
It would be quite nice if you could you split this into two commits and submit them one at a time so travis sees each one:
This way we can prove the compatability module works But I'm not fussed if you don't want to, I'm still happy to merge this as is |
dd9d4f0
to
b99f027
Compare
a future release, so it is recommended to update all package references. | ||
""" | ||
|
||
warnings.warn(DEPRECATION_MESSAGE, DeprecationWarning) |
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.
DeprecationWarning
is ignored by default, but would seem to be the semantically correct choice here.
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.
nice
I understand the philosophy of why you'd want to split this up, but I'm not inclined to put in the extra work to make it happen. |
b99f027
to
e39ff7e
Compare
Rebased to edit the commit with broken README.rst. |
@@ -1,7 +1,10 @@ | |||
0.3.2 (unreleased) | |||
------------------ | |||
|
|||
- Nothing changed yet. | |||
- Change the name of the package to `sqlalchemy_redshift` to match the naming | |||
convention for other dialects; the `redshift_sqlalchemy` now references |
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.
missed a word? Should this be "the deprecated redshift_sqlalchemy
now references..."?
e39ff7e
to
a1f6994
Compare
Updated the CHANGELOG message. |
Perfect! Merge when ready |
Rename package to sqlalchemy_redshift
Fixes #40.