On Fri, Jul 18, 2008 at 11:55 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> This is an example of the problem with doctest -- it's easy to
> overspecify the tests. I don't think that whether the repr() of a
> Decimal uses single or double quotes should be considered a spec cast
> in stone by d
The new float.hex() is really nice. Would like to augment it with a matching float.bin() method using the same notation and
normalization and leaving all the rightmost bits as Guido suggested. I think this would help demystify floats and make it
straightforward to show exactly what is happening
Meant to copy list on reply, sorry.
-- Forwarded message --
From: Karen Tracey <[EMAIL PROTECTED]>
Date: Fri, Jul 18, 2008 at 11:48 PM
Subject: Re: [Python-Dev] Change in repr of Decimal in 2.6
To: Raymond Hettinger <[EMAIL PROTECTED]>
On Fri, Jul 18, 2008 at 11:19 PM, Raymond He
This is an example of the problem with doctest -- it's easy to
overspecify the tests. I don't think that whether the repr() of a
Decimal uses single or double quotes should be considered a spec cast
in stone by doctests.
On Fri, Jul 18, 2008 at 8:19 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
From: Karen Tracey
I noticed when trying out Python's 2.6b2 release that the repr of Decimal has
changed since 2.5. On 2.5:
...
quotes were used whereas on 2.6b2:
...
single quotes are used. Searching around I see this was done in r60773 with
the log message:
Fix decimal repr which shoul
[Originally posted to python-list but on further reflection and some
feedback I think it might be more appropriate here.]
I noticed when trying out Python's 2.6b2 release that the repr of Decimal
has changed since 2.5. On 2.5:
Python 2.5.1 (r251:54863, Mar 7 2008, 04:10:12)
[GCC 4.1.3 20070929
Josiah Carlson wrote:
It's entirely possible that I know very little about what was being
made available via the bsddb module, but to match the API of what is
included in the documentation (plus the dictionary interface that it
supports) shouldn't be terribly difficult.
Maybe for new databases,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
| On Sun, May 25, 2008 at 6:25 AM, Jesus Cea <[EMAIL PROTECTED]> wrote:
|> Since I need to port bsddb3 to py3k, what I need to know?. Is any
|> *updated* document out there?.
|
| No, but there is a not yet complete, but quite up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Cannon wrote:
| On Thu, Jul 17, 2008 at 7:37 PM, Guido van Rossum <[EMAIL PROTECTED]>
wrote:
|> On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
|>> On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote:
|>>> bsddb is in a ver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
| bsddb is in a very bad shape, as the 2.6 code hasn't been merged into
| 3k. I somewhat doubt that this gets resolved before the release, so
| bsddb users might need to skip 3.0.
Working on the 3.0 port just now. 03:40 in the
On Thu, Jul 17, 2008 at 11:42 AM, Shane Hathaway <[EMAIL PROTECTED]> wrote:
> ranjith kannikara wrote:
>>
>> As a student I am not familiar with Restricted Python and python AST
>> implementation.And in need of help to start the Restricted Python
>> implementation.
>
> Here is some context for Pyth
...
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
ranjith kannikara wrote:
As a student I am not familiar with Restricted Python and python AST
implementation.And in need of help to start the Restricted Python
implementation.
Here is some context for Python-Dev.
RestrictedPython is a custom Python compiler that, when combined with a
restrict
On Fri, Jul 18, 2008 at 12:54 PM, Bill Janssen <[EMAIL PROTECTED]> wrote:
> Why is it you're trying to use "git"?
Neil set up a mirror and I was curious. Same with the bzr mirror.
-Brett
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyth
On 2008-07-18 21:35, Charles Hixson wrote:
Invariably, when someone goes and removes a module, someone else is
going to complain, "but I used feature X, not having feature X will
break my code." We, as maintainers can then say, "if you cared,
maintain it." But I'm not sure that is the greatest
On Fri, Jul 18, 2008 at 6:10 PM, Eric Smith
<[EMAIL PROTECTED]> wrote:
> Do we want to document the actual behavior, or do we want to normalize all
> platforms so that they all return 'nan' and 'inf'?
I seem to recall that Christian Heimes recently put some work into
making sure that repr() or str
Sidnei da Silva schrieb:
> On Fri, Jul 18, 2008 at 12:42 PM, Sidnei da Silva
> <[EMAIL PROTECTED]> wrote:
>> That's a great trick! I seem to remember that there is a way to turn
>> that off globally though, but not sure where. Maybe running
>> drwtsn32.exe and un-checking 'Visual Notification' does
Why is it you're trying to use "git"?
Bill
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Eric Smith schrieb:
georg.brandl wrote:
Author: georg.brandl
Date: Fri Jul 18 13:15:06 2008
New Revision: 65099
Log:
Document the different meaning of precision for {:f} and {:g}.
Also document how inf and nan are formatted. #3404.
Thanks for doing this. But see this output:
http://www.pytho
On Fri, Jul 18, 2008 at 12:35 PM, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 18, 2008 at 12:07:19PM -0700, Brett Cannon wrote:
>> I lied. Trying again complained about Mac/IDLE/Makefile.in which I
>> have not touched, nor is it listed as changed.
>
> I think you are running into the
On Friday 18 July 2008 07:57:01 am Josiah Carlson wrote:
> On Fri, Jul 18, 2008 at 7:21 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On Thu, Jul 17, 2008 at 10:43 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> >> On Thu, Jul 17, 2008 at 7:37 PM, Guido van Rossum <[EMAIL PROTECTED]>
wrote:
>
On Fri, Jul 18, 2008 at 12:07:19PM -0700, Brett Cannon wrote:
> I lied. Trying again complained about Mac/IDLE/Makefile.in which I
> have not touched, nor is it listed as changed.
I think you are running into the fact that the git tree on
code.python.org is only updated every 30 minutes. Using th
On Fri, Jul 18, 2008 at 12:31 PM, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 18, 2008 at 11:57:21AM -0700, Brett Cannon wrote:
>> I figured this out. I just did ``git reset --hard``, did the proper
>> "fetch;rebase" dance, resolved the conflict, did ``git add`` and then
>> continued
On Fri, Jul 18, 2008 at 11:57:21AM -0700, Brett Cannon wrote:
> I figured this out. I just did ``git reset --hard``, did the proper
> "fetch;rebase" dance, resolved the conflict, did ``git add`` and then
> continued with the rebase. It all looks fine now.
Doing a fetch followed by a rebase is simi
Nick Coghlan writes:
> And downloading pybsddb and installing really shouldn't be all that
> difficult :)
It shouldn't be, but lots of "enterprise"[1] environments will require
qualifying the "new" package according to corporate standards.
I won't argue that this is a sufficient reason to kee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 18, 2008, at 2:32 PM, A.M. Kuchling wrote:
We can obviously drop the module for 3.0. For 2.x, should we just
shrug and disable most of the BerkeleyDB tests (maybe just on Windows)
by adding a new resource to enable them? If we're stuck with
On Fri, Jul 18, 2008 at 11:03 AM, Fred Drake <[EMAIL PROTECTED]> wrote:
> On Jul 18, 2008, at 1:45 PM, Josiah Carlson wrote:
>>
>> It's entirely possible that I know very little about what was being
>> made available via the bsddb module, but to match the API of what is
>> included in the documenta
On Fri, Jul 18, 2008 at 11:57 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 18, 2008 at 11:37 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> On Fri, Jul 18, 2008 at 11:12 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>>> On Thu, Jul 17, 2008 at 11:54 PM, Neil Schemenauer <[EMAIL PROTECTED
On Fri, Jul 18, 2008 at 11:12:41AM -0700, Brett Cannon wrote:
> >git log git-svn..
>
> And those two periods are significant for people who think they are
> line noise. Damn is Git quirky.
I guess it would have been clearer if I had used "git-svn..HEAD".
The ".." is similar to SVN's ":" so I
On Fri, Jul 18, 2008 at 11:37 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 18, 2008 at 11:12 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> On Thu, Jul 17, 2008 at 11:54 PM, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
>>> [back on the list]
>>>
>>> On Thu, Jul 17, 2008 at 11:24:16PM -0
On Fri, Jul 18, 2008 at 11:12:41AM -0700, Brett Cannon wrote:
> And those two periods are significant for people who think they are
> line noise. Damn is Git quirky.
Oh my, yes. We use git at work; there's a reason I now use Bazaar for
personal projects.
> I assume the ^ operator means "just bef
On Fri, Jul 18, 2008 at 11:12 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 11:54 PM, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
>> [back on the list]
>>
>> On Thu, Jul 17, 2008 at 11:24:16PM -0700, Brett Cannon wrote:
>>> Turned out to be a rebuild::
>>>
>>>
>>> r6507
yOn Fri, Jul 18, 2008 at 10:45:06AM -0700, Josiah Carlson wrote:
>> It's entirely possible that I know very little about what was being
> made available via the bsddb module, but to match the API of what is
> included in the documentation (plus the dictionary interface that it
> supports) shouldn't
Fred Drake wrote:
On Jul 18, 2008, at 1:45 PM, Josiah Carlson wrote:
It's entirely possible that I know very little about what was being
made available via the bsddb module, but to match the API of what is
included in the documentation (plus the dictionary interface that it
supports) shouldn't b
On Thu, Jul 17, 2008 at 11:54 PM, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
> [back on the list]
>
> On Thu, Jul 17, 2008 at 11:24:16PM -0700, Brett Cannon wrote:
>> Turned out to be a rebuild::
>>
>>
>> r65077 = 82d954e8c20c91562c4c660859d17756cba10992
>> r65082 = 1c75cce93c2ef2ec87e8018886
On Fri, Jul 18, 2008 at 7:21 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 10:43 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> On Thu, Jul 17, 2008 at 7:37 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>>> On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]
On Jul 18, 2008, at 1:45 PM, Josiah Carlson wrote:
It's entirely possible that I know very little about what was being
made available via the bsddb module, but to match the API of what is
included in the documentation (plus the dictionary interface that it
supports) shouldn't be terribly difficul
On Fri, Jul 18, 2008 at 8:11 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 18, 2008 at 7:57 AM, Josiah Carlson
> <[EMAIL PROTECTED]> wrote:
>> Invariably, when someone goes and removes a module, someone else is
>> going to complain, "but I used feature X, not having feature X will
>
georg.brandl wrote:
Author: georg.brandl
Date: Fri Jul 18 13:15:06 2008
New Revision: 65099
Log:
Document the different meaning of precision for {:f} and {:g}.
Also document how inf and nan are formatted. #3404.
Thanks for doing this. But see this output:
http://www.python.org/dev/buildbot/al
Thomas Heller <[EMAIL PROTECTED]> writes:
> The most annoying thing on the windows buildbots is when Python crashes hard
> (with a general protection fault or stack overflow, for example).
> Usually the system pops up a dialog in this case which allows to
> attach a debugger to the process. This
ACTIVITY SUMMARY (07/11/08 - 07/18/08)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
1967 open (+38) / 13262 closed (+25) / 15229 total (+63)
Open issues with patches: 619
Average
On Fri, Jul 18, 2008 at 12:42 PM, Sidnei da Silva
<[EMAIL PROTECTED]> wrote:
> That's a great trick! I seem to remember that there is a way to turn
> that off globally though, but not sure where. Maybe running
> drwtsn32.exe and un-checking 'Visual Notification' does the trick?
FWIW, here's a kb
On Fri, Jul 18, 2008 at 4:14 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> The most annoying thing on the windows buildbots is when Python crashes hard
> (with a general protection fault or stack overflow, for example).
> Usually the system pops up a dialog in this case which allows to
> attach a
On Fri, Jul 18, 2008 at 7:57 AM, Josiah Carlson
<[EMAIL PROTECTED]> wrote:
> Invariably, when someone goes and removes a module, someone else is
> going to complain, "but I used feature X, not having feature X will
> break my code." We, as maintainers can then say, "if you cared,
> maintain it."
On Fri, Jul 18, 2008 at 7:21 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 10:43 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> On Thu, Jul 17, 2008 at 7:37 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>>> On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]
On Thu, Jul 17, 2008 at 10:43 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 7:37 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
>>> On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote:
bsddb
On Fri, Jul 18, 2008 at 3:24 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Antoine Pitrou wrote:
>>
>> Guido van Rossum python.org> writes:
>>>
>>> Thanks Barry! Indeed, I want everyone to focus on stabilization and
>>> release blockers (and the occasional speed-up). Be extra careful with
>>> what
Nick Coghlan gmail.com> writes:
>
> Before beta 3, I think if we need minor features (such as re.ASCII) to
> fix fairly major bugs (re.IGNORECASE not working properly by default in
> Py3k) then they should probably go in (case by case permission still
> needed from Barry or Guido though, as wi
Antoine Pitrou wrote:
Guido van Rossum python.org> writes:
Thanks Barry! Indeed, I want everyone to focus on stabilization and
release blockers (and the occasional speed-up). Be extra careful with
what you submit between now and October, ask for a code review unless
you're really sure. Also, re
Guido van Rossum python.org> writes:
>
> Thanks Barry! Indeed, I want everyone to focus on stabilization and
> release blockers (and the occasional speed-up). Be extra careful with
> what you submit between now and October, ask for a code review unless
> you're really sure. Also, remember, NO NEW
The most annoying thing on the windows buildbots is when Python crashes hard
(with a general protection fault or stack overflow, for example).
Usually the system pops up a dialog in this case which allows to
attach a debugger to the process. This dialog will stay open until
the maintainer manually
51 matches
Mail list logo
