-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antoine Pitrou wrote:
> I agree about performance but I don't think it's right to say we can fix
> stability later. This is a storage module, and people risk losing their data
> if
> there are glaring bugs. If we really want an efficient dbm-compatibl
2008/9/10 Fred Drake <[EMAIL PROTECTED]>:
> On Sep 10, 2008, at 5:23 AM, M.-A. Lemburg wrote:
>> I actually find it helpful to have the PyPI packages that ended up in
>> the stdlib use different names, since that opens up the possibility
>> to use the more current releases from PyPI in an applicati
On Sep 10, 2008, at 5:23 AM, M.-A. Lemburg wrote:
I actually find it helpful to have the PyPI packages that ended up in
the stdlib use different names, since that opens up the possibility
to use the more current releases from PyPI in an application.
I'm with Marc-Andre on this; using the same
M.-A. Lemburg wrote:
> On 2008-09-10 00:26, [EMAIL PROTECTED] wrote:
>> mal> Besides, what's so bad with downloading and installing a package
>> mal> from PyPI ?
>>
>> Nothing, I do it all the time. But my impression is that when an external
>> module moves into the core it frequently unde
On 2008-09-10 00:26, [EMAIL PROTECTED] wrote:
> mal> Besides, what's so bad with downloading and installing a package
> mal> from PyPI ?
>
> Nothing, I do it all the time. But my impression is that when an external
> module moves into the core it frequently undergoes some type of name cha
mal> Besides, what's so bad with downloading and installing a package
mal> from PyPI ?
Nothing, I do it all the time. But my impression is that when an external
module moves into the core it frequently undergoes some type of name change
(e.g. pysqlite vs sqlite3 or Optik vs optparse) eve
On 2008-09-09 21:49, Antoine Pitrou wrote:
> Josiah Carlson gmail.com> writes:
>> While the wrapper for sqlite to offer
>> a dbm-like interface is relatively untested (it does have testcases
>> thanks to Skip), dealing with a couple-hundred (at most) line wrapper
>> is far more reasonable for test
Josiah Carlson gmail.com> writes:
>
> While the wrapper for sqlite to offer
> a dbm-like interface is relatively untested (it does have testcases
> thanks to Skip), dealing with a couple-hundred (at most) line wrapper
> is far more reasonable for testing, verification, bugfixing, etc.,
> than the
Given that the *API* is fixed though, it is probably better to have the
module present in 3.0 and bring it back to the main line in 2.7.
If any absolute clangers from a performance/stability point of view get
past Raymond (and everyone else with an interest in this) then they can
be addressed in
On Tue, Sep 9, 2008 at 3:31 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
> Nick Coghlan gmail.com> writes:
>>
>> Given that the *API* is fixed though, it is probably better to have the
>> module present in 3.0 and bring it back to the main line in 2.7.
>>
>> If any absolute clangers from a perfor
Nick Coghlan gmail.com> writes:
>
> Given that the *API* is fixed though, it is probably better to have the
> module present in 3.0 and bring it back to the main line in 2.7.
>
> If any absolute clangers from a performance/stability point of view get
> past Raymond (and everyone else with an int
11 matches
Mail list logo
