On Wed, Sep 3, 2008 at 8:41 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm not going to release rc1 tonight. There are too many open release
> blockers that I don't want to defer, and I'd like the buildbots to churn
> through the bsddb removal
On Thu, Sep 4, 2008 at 1:05 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>
> On Sep 4, 2008, at 3:51 PM, Guido van Rossum wrote:
>
>> I'm a little confused -- why did you remove the release notes for
>> previous betas but leave those for the alphas in place? ISTM that the
>> file was an accumulation
Jesus Cea wrote:
> This is true. But python uses openssl, for example, and it must be
> updated from time to time, for example. The only difference is that the
> bugs are not discovered by python.
>
> In fact, I can say that Berkeley DB 4.7 snapshot releases crashed a lot
> with bsddb testsuite. B
Guido van Rossum wrote:
> On Thu, Sep 4, 2008 at 8:47 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>> Jesus Cea jcea.es> writes:
>>> First we had "thread.setDaemon()". This was not PEP8, so Python 3.0
>>> renamed it to "thread.set_daemon()". Lately Python 3.0 changes the
>>> method to an attribut
On Wed, Sep 3, 2008 at 8:41 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm not going to release rc1 tonight. There are too many open release
> blockers that I don't want to defer, and I'd like the buildbots to churn
> through the bsddb removal
On Thu, Sep 4, 2008 at 1:56 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 4, 2008 at 8:47 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>> Jesus Cea jcea.es> writes:
>>>
>>> First we had "thread.setDaemon()". This was not PEP8, so Python 3.0
>>> renamed it to "thread.set_daemon()".
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 3:51 PM, Guido van Rossum wrote:
I'm a little confused -- why did you remove the release notes for
previous betas but leave those for the alphas in place? ISTM that the
file was an accumulation of release notes throughout the vari
On Thu, Sep 4, 2008 at 8:47 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
> Jesus Cea jcea.es> writes:
>>
>> First we had "thread.setDaemon()". This was not PEP8, so Python 3.0
>> renamed it to "thread.set_daemon()". Lately Python 3.0 changes the
>> method to an attribute "thread.daemon".
>>
>> I
On Wed, Sep 3, 2008 at 9:25 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> [Brett]
>>
>> I gave a talk last night at the Vancouver Python users group on
>> 2.6/3.0, and I tried the following code and it failed during a live
>> demo::
>>
>> >>> try: pass
>> ... except Exception, Exception: pas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 2:33 PM, Jesus Cea wrote:
* I will try to find another Python area of interest to me, to fully
honor my commit privileges.
BTW Jesus, if you want to maintain the code on python.org, we can
create an area in the sandbox for you
On Thu, Sep 4, 2008 at 11:33 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Guido van Rossum wrote:
>> I am still in favor of removing bsddb from Python 3.0.
>
> BDFL has talked.
>
> I want to record this:
>
> * I will keep maintaining bsddb in Python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guido van Rossum wrote:
> I am still in favor of removing bsddb from Python 3.0.
BDFL has talked.
I want to record this:
* I will keep maintaining bsddb in Python 2.6. No idea what is the plan
for 2.7, nevertheless.
* I will keep bsddb updated and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 1:57 PM, Guido van Rossum wrote:
I am still in favor of removing bsddb from Python 3.0. It depends on a
3rd party library of enormous complexity whose stability cannot always
be taken for granted. Arguments about code ownership, r
[I don't know who added my Google address to the CC list. Please don't
do that again.]
On Thu, Sep 4, 2008 at 10:07 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Sep 4, 2008, at 12:20 PM, Jesus Cea wrote:
>
>> I'm a bit worried about you restoring bsddb and be pulled-off shortly
>> again if I c
[I don't know who added my Google address to the CC list. Please don't
do that again.]
On Thu, Sep 4, 2008 at 10:07 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Sep 4, 2008, at 12:20 PM, Jesus Cea wrote:
>
>> I'm a bit worried about you restoring bsddb and be pulled-off shortly
>> again if I c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 12:20 PM, Jesus Cea wrote:
I'm a bit worried about you restoring bsddb and be pulled-off shortly
again if I can't resolve any remaining issues in minutes :). But I
would
take the risk.
Don't worry about that. Guido's decisio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raymond Hettinger wrote:
> [Barry]
>> Since rc1 did not go out last night, bsddb could be restored. I
>> still don't think it should be, but at this point it's up to Guido
>> to override, and I will abide by his decision.
>
> Put in my vote for res
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregory P. Smith wrote:
> The fact that the Python Lib/bsddb/test/ test suite has uncovered
> actual Oracle/Sleepycat BerkeleyDB bugs in supposedly stable releases
> has always disturbed me.
This is true. But python uses openssl, for example, and it m
Jesus Cea jcea.es> writes:
>
> First we had "thread.setDaemon()". This was not PEP8, so Python 3.0
> renamed it to "thread.set_daemon()". Lately Python 3.0 changes the
> method to an attribute "thread.daemon".
>
> I think the last change is risky, because you can mistype and create a
> new attri
On Thu, Sep 4, 2008 at 11:39 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Jesus Cea wrote:
>>
>> I would rather revert to the method style, or redo the class to avoid
>> new attribute creation, maybe via some "thread.__setattr__()" magic.
>
> Or maybe with __slots__ in the threading class. It'
Jesus Cea wrote:
I would rather revert to the method style, or redo the class to avoid
new attribute creation, maybe via some "thread.__setattr__()" magic.
Or maybe with __slots__ in the threading class. It'd also safe some
memory and subclasses of Threading still work as expected.
Christian
[Barry]
Since rc1 did not go out last night, bsddb could be restored. I still
don't think it should be, but at this point it's up to Guido to
override, and I will abide by his decision.
Put in my vote for restoration, deprecation, and thought-out
removal/replacement in 3.1.
The ensuing dis
On Thu, Sep 4, 2008 at 11:03 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> First we had "thread.setDaemon()". This was not PEP8, so Python 3.0
> renamed it to "thread.set_daemon()". Lately Python 3.0 changes the
> method to an attribute "thread.daemo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since rc1 did not go out last night, bsddb could be restored. I still
don't think it should be, but at this point it's up to Guido to
override, and I will abide by his decision.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Dar
2008/9/4 Jesus Cea <[EMAIL PROTECTED]>:
> PS: If you mistype the method name, you get an error. If you mistype the
> attribute assignment, the bug goes unnoticed.
I'm neutral over the threading change, but this is a good point to
consider in general as part of the "method vs property" question whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First we had "thread.setDaemon()". This was not PEP8, so Python 3.0
renamed it to "thread.set_daemon()". Lately Python 3.0 changes the
method to an attribute "thread.daemon".
I think the last change is risky, because you can mistype and create a
new a
[Brett Cannon]
On Wed, Sep 3, 2008 at 7:33 PM, <[EMAIL PROTECTED]> wrote:
All but dbm.dumb require some pre-existing library to exist to compile
against. So any platform that has the proper libraries installed will
be able to use ndbm or gnu, but as for which platforms that are I do
not know.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 9:45 AM, [EMAIL PROTECTED] wrote:
Barry> Or did he commit Mark's patch from bug 3772? If so, that
would
Barry> count as a reviewed patch.
The checkin message says issue 3726:
Author: vinay.sajip
Date: Wed Sep 3
2008/9/4 Brett Cannon <[EMAIL PROTECTED]>:
> On Wed, Sep 3, 2008 at 7:33 PM, <[EMAIL PROTECTED]> wrote:
> All but dbm.dumb require some pre-existing library to exist to compile
> against. So any platform that has the proper libraries installed will
> be able to use ndbm or gnu, but as for which pl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 1:08 AM, Gregory P. Smith wrote:
Frankly I don't see a big deal with not including it in *3.0* so long
as a reference to where to download it as an add on (jcea's pybsddb
site) is included in the release notes and PEP 3108. I've
Barry> Or did he commit Mark's patch from bug 3772? If so, that would
Barry> count as a reviewed patch.
The checkin message says issue 3726:
Author: vinay.sajip
Date: Wed Sep 3 11:20:05 2008
New Revision: 66180
Log:
Issue #3726: Allowed spaces in separators in logg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 7:31 AM, Facundo Batista wrote:
(I'll be hanging around in #python-dev today and tomorrow, btw, ping
me if I can help you)
Me too, though I'm a bit busy at work. Ping my nick 'barry' if you
need any RM-level decision.
- -Ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 7:08 AM, [EMAIL PROTECTED] wrote:
Barry> In addition, Mark reported in IRC that there are some
regressions
Barry> in the logging module.
Vinay apparently checked in some changes to the logging module with no
review. In
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 3:28 AM, Mark Hammond wrote:
Barry writes:
In addition, Mark reported in IRC that there are some regressions in
the logging module.
3772 logging module fails with non-ascii data
Which according to the IRC discussion doesn't a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 4, 2008, at 12:14 AM, Raymond Hettinger wrote:
[Barry]
I'm not going to release rc1 tonight.
Can I go ahead with some bug fixes and doc improvements
or should I wait until after Friday?
Doc fixes are fine. Please have bug fix patches re
2008/9/4 Raymond Hettinger <[EMAIL PROTECTED]>:
> Can I go ahead with some bug fixes and doc improvements
> or should I wait until after Friday?
Doc improvements: go ahead.
Bug fixes: the patchs should be revised by other developer.
(I'll be hanging around in #python-dev today and tomorrow, btw
Barry> In addition, Mark reported in IRC that there are some regressions
Barry> in the logging module.
Vinay apparently checked in some changes to the logging module with no
review. In the absence of obvious bug fixes there that should probably be
reverted.
Skip
Brett> All but dbm.dumb require some pre-existing library to exist to
Brett> compile against. So any platform that has the proper libraries
Brett> installed will be able to use ndbm or gnu, but as for which
Brett> platforms that are I do not know.
Wasn't bsddb (either bsddb185 or
>> Start raising some pitchforks. It looks like Raymond will join the
>> march :).
>
>Sorry, I know the word ("pitchfork"), but I don't understand the meaning
>you want to communicate. English is not my native language.
The farmers march on town hall as a mob, carrying their pitchforks,
when the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Barry Warsaw wrote:
>> Can I do anything to revert this decision?. If not, what can I do to be
>> reconsidered in 3.1?.
>
> Start raising some pitchforks. It looks like Raymond will join the
> march :).
Sorry, I know the word ("pitchfork"), but I do
Barry writes:
> In addition, Mark reported in IRC that there are some regressions in
> the logging module.
3772 logging module fails with non-ascii data
Which according to the IRC discussion doesn't apply to py3k. The fix for
2.6 is quite trivial...
Cheers,
Mark
_
41 matches
Mail list logo
