GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||
GeezerVison is showing github.com — gh-93057: Deprecate positional use of optional sqlite3.connect() params by erlend-aasland · Pull Request #107948 · python/cpython Conversation
|
Ah, of course. That's tricky. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Please add a test for connect() and mention this change in What's New and NEWS entries.
It is a wart that we will get two warnings, but there is no simple way to avoid it, except applying deprecations one at a time -- first in connect(), then (since 3.15) in Connection. Not sure if it it is worth.
We can also convert all positional arguments in connect() into keyword arguments for factory. It is a lot of complex code.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
No, that is a backwards incompatible change. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Is the existing NEWS and What's New entries insufficient? In what way? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Ah, they already mention connect()! Then simply add "and the Connection constructor". |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Yeah, that's useful information. I'll add that; thanks. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks for the review, Serhiy. Much appreciated. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
@felixxm, sorry, I forgot to ping you; I hope not these deprecations will create havoc for Django. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
All good, Django doesn't pass these positional params, only a database name. Thanks 👍 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.