Skip to content
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

DM-9918: Robustify sqlite use #52

Merged
merged 2 commits into from Apr 24, 2017
Merged

DM-9918: Robustify sqlite use #52

merged 2 commits into from Apr 24, 2017

Conversation

PaulPrice
Copy link
Contributor

No description provided.

if haveSqlite3 and re.match(r'.*\.sqlite3', location):
if re.match(r'.*\.sqlite3', location):
if not haveSqlite3:
raise RuntimeError("sqlite3 registry specified (%s), but unable to import sqlite3 module" %
Copy link
Contributor

Choose a reason for hiding this comment

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

this line looks longer than 80 chars (is that rule official yet?) and are we preferring .format to % string substitution now?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

On both points I have followed the current style in that file.

If we're given a sqlite3 registry, then the user expects us
to use it. But if we failed to import the sqlite3 module then
there's nothing we can do so we should raise an exception.
It doesn't make sense for the PosixRegistry to be a file.
@PaulPrice PaulPrice merged commit e4f6c06 into master Apr 24, 2017
@ktlim ktlim deleted the tickets/DM-9918 branch August 25, 2018 06:15
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.

None yet

2 participants