Actually both sqlite3.version and sqlite3.version_info, the former as a string,
the latter as a tuple.
E
On 15 Oct 2020, at 14:45, Erlend Aasland
mailto:erlen...@innova.no>> wrote:
FYI, sqlite3 has a pysqlite “version" attribute iso. “__version__", stemming
from its days o
FYI, sqlite3 has a pysqlite “version" attribute iso. “__version__", stemming
from its days outside of stdlib. It has held the value “2.6.0" since commit
f9cee22, 2010-03-05.
Erlend E. Aasland
On 14 Oct 2020, at 15:53, Serhiy Storchaka
mailto:storch...@gmail.com>> wrote:
Some module
Hi, everyone.
I'm trying to find a reviewer for this trivial PR:
https://github.com/python/cpython/pull/20530
(The PR fixes CheckTraceCallbackContent (in the sqlite3 test suite) for SQLite
pre 3.7.15.)
I've given up hunting for alternative reviewers (a process I find very
uncomfortable,
> On 5 Jan 2021, at 09:08, Serhiy Storchaka wrote:
> 27.12.20 22:20, Erlend Aasland пише:
>> Who can help me review code that touches the sqlite3 module code base?
>
> I fixed many bugs in sqlite3 and did reviews, so I have some experience,
> although I am not an expert. I
On 27 Dec 2020, at 22:38, Christian Heimes
mailto:christ...@python.org>> wrote:
On 27/12/2020 21.20, Erlend Aasland wrote:
[…]
Who can help me review code that touches the sqlite3 module code base?
as far as I know we don't have an active module owner and maintainer any
more.
What about
> On 4 Jan 2021, at 17:34, Steve Dower wrote:
> On 12/28/2020 11:32 AM, Erlend Aasland wrote:
>>> On 27 Dec 2020, at 22:38, Christian Heimes >> <mailto:christ...@python.org>> wrote:
>>> How about you put your name in the expert index instead of him? :)
>
> On 4 Jan 2021, at 18:24, Guido van Rossum wrote:
>
> OTOH if you just want to have the PR merged I can do that -- it seems
> unobjectionable.
I'm eager to get it merged, so I'll appreciate it if you could help with that.
Erlend
___
Python-Dev
Ref. https://bugs.python.org/issue43908, I've compiled a list of types that
have been converted to heap types. I've posted it on Discourse for readability:
https://discuss.python.org/t/list-of-built-in-types-converted-to-heap-types/8403
Note: for now, I didn't bother to trace PyType_Spec
Hi all,
What's the recommended approach with issues like
https://bugs.python.org/issue43094? Change the docs or the implementation? I
did a quick search on bpo, but could not find similar past issues.
Erlend
___
Python-Dev mailing list --
Hi Victor, and thanks for you reply.
> On 9 Feb 2021, at 11:46, Victor Stinner wrote:
> If there are applications relying on the parameter name, it's better
> to trust the Python implementation, rather than the documentation.
I feared that answer :)
> It would be better to make these
> On 10 Feb 2021, at 01:28, Petr Viktorin wrote:
>
> On 2/9/21 9:15 PM, Serhiy Storchaka wrote:
>> 09.02.21 12:22, Erlend Aasland пише:
>>> What's the recommended approach with issues like
>>> https://bugs.python.org/issue43094? Change the docs or the implemen
Thanks, Jakub.
E
> On 9 Feb 2021, at 19:42, Jakub Stasiak wrote:
>
> To provide some context as you looked for issues on bpo: in the two I was
> involved in[1][2] the resolution was to update the documenttion to reflect
> the actual situation.
>
> Best,
> Jakub
>
> [1]
Hi, Marco! I'd suggest taking a look at the issues that are marked as "Easy
Tasks" on http://bugs.python.org. Not all of them are trivial, though (there
may not be consensus on how to solve the issue), but you should be able to find
something to work on there :)
Erlend
On 26 Mar 2021, at
Glad to help! Thank you Guido, Antoine, Serhiy, and Victor for your insights
and scrutinising :)
E
On 25 Mar 2021, at 18:15, Guido van Rossum
mailto:gu...@python.org>> wrote:
I’m glad there is more clarity here. And thanks to Erlend Egeberg Aasland for
championing the PR!
—Guido
On Thu,
On 20 Sep 2021, at 13:18, Pablo Galindo Salgado
mailto:pablog...@gmail.com>> wrote:
We are doing this work in this branch:
https://github.com/we-like-parsers/cpython/blob/fstring-grammar
That link is broken. Assuming you mean
https://github.com/we-like-parsers/cpython/tree/fstring-grammar?
Is there an issue that keeps track of all the missing pieces? A "remaining
tasks" list would be useful for involving more devs (and of course useful when
resuming development, "now, where was I..."). A quick search on BPO revealed
some info:
- bpo-46313: SSLObject does not raise SSLEOFError on
Petr, SC, thanks for your time and response! Just a quick comment:
> On 8 Feb 2022, at 11:32, Petr Viktorin wrote:
>
> In effect, the SC accepts the first part of the PEP, except cases where:
What status does that put the PEP in?
E
___
Python-Dev
According to the docs[^1], MSVC does _not_ support all of C99. OTOH they claim
conformance with both C11 and C17, using the /std:c11 and /std:c17 compiler
flags.
[^1]:
https://docs.microsoft.com/en-us/cpp/build/reference/std-specify-language-standard-version?view=msvc-170
> On 8 Feb 2022, at
18 matches
Mail list logo
