Tim Lyons added the comment:
Surely the user of getlocale as the right to expect that the same thing (i.e.
ISO language codes) would be returned on all platforms. I am looking at some
code that provides special purpose date handling routines. The appropriate
routine is selected by a language
Tim Golden added the comment:
But at the least, the start of the para might be slightly reworded to something
like: "If you specifically need to avoid name clashes with subclasses, there is
limited support..." which avoids the phrase "Since there is a valid use-case
for class-
Tim Golden added the comment:
It's almost certainly coming straight back from the O/S,
where Python is doing its usual thing of channelling
an O/S error directly. Obviously we could special-case
this or any other specific error; but we usually don't
--
nosy: +
Tim Golden added the comment:
I'm not quite sure how anyone's supposed to determine
which bugs are likely to have been worked around and
which haven't :) I'm also unsure why a clear bugfix
shouldn't make it into a minor version release. Surely
this isn't the only
Tim Golden added the comment:
Reopening as there seems to be some possibility of progress
--
nosy: -BreamoreBoy
resolution: invalid ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/
Changes by Tim Golden :
--
versions: +Python 3.3 -Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue1602>
___
___
Python-bugs-list mailin
Tim Alexander added the comment:
Wanted to quickly comment here, as I'm dealing with this issue as well, that I
did find a workaround for avoiding it as far back as 2.6 (and it's not "don't
pass a Pipe through a Pipe")
multiprocessing.reduction can already do this
New submission from Tim Perevezentsev :
This code:
assert type(val) is StringType,"Header values must be strings"
(from here
http://svn.python.org/view/python/tags/r271/Lib/wsgiref/handlers.py?revision=86833&view=markup)
from "start_response" method, is not allowi
Tim Perevezentsev added the comment:
str - immutable. So every str subclass object is normal string. I don't see any
design violation here.
--
___
Python tracker
<http://bugs.python.org/is
Tim Wilcoxson <[EMAIL PROTECTED]> added the comment:
I guess my only reply isfair enough.
heh.
On Thu, May 22, 2008 at 1:07 PM, Kurt B. Kaiser <[EMAIL PROTECTED]>
wrote:
>
> Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment:
>
> When this is running, what
Tim Peters <[EMAIL PROTECTED]> added the comment:
Strongly doubt this has anything to do with random number generation.
Python maintains a freelist for float objects, which is both unbounded
and immortal. Instead of doing "data[i] = random()", do, e.g., "data[i]
= float(
Tim Peters <[EMAIL PROTECTED]> added the comment:
They stayed alive simultaneously because you stored 100 million of them
simultaneously in a list (data[]). If instead you did, e.g.,
for i in xrange(1):
x = random()
the problem would go away -- then only two float objec
Tim Peters <[EMAIL PROTECTED]> added the comment:
Float objects also require, as do all Python objects, space to hold a
type pointer and a reference count. So each float object requires at
least 16 bytes (on most 32-bit boxes, 4 bytes for the type pointer, 4
bytes for the refcount, + 8
Tim Golden <[EMAIL PROTECTED]> added the comment:
The _multiprocessing module is not building under Windows at the moment.
Attempting to import multiprocessing (from an .exe build from the
current svn) gives "ImportError: No module named _multiprocessing" and
the test suite sk
Tim Golden <[EMAIL PROTECTED]> added the comment:
Benjamin Peterson wrote:
> Benjamin Peterson <[EMAIL PROTECTED]> added the comment:
>
> On Wed, Jun 11, 2008 at 9:20 AM, Tim Golden <[EMAIL PROTECTED]> wrote:
>> Tim Golden <[EMAIL PROTECTED]> added the com
Tim Golden <[EMAIL PROTECTED]> added the comment:
I'm sorry; I've had a look and there's no chance of my updating the
solution and project files by hand; and I can't run Visual Studio at the
moment. I'll try emailing Trent or Christian in the hope that o
Tim Golden <[EMAIL PROTECTED]> added the comment:
Trent's supplied me with enough info to patch the project files
manually. The attached patch against r64120 results in the
_multiprocessing module building. I'm running the tests now but I'll
upload the patch in any ca
Tim Golden <[EMAIL PROTECTED]> added the comment:
Giampaolo Rodola' wrote:
> New submission from Giampaolo Rodola' <[EMAIL PROTECTED]>:
>
> By using:
> http://www.python.org/dev/daily-msi/python-2.6.14041.msi
>
>
> C:\>C:\python26\python
>
Tim Golden <[EMAIL PROTECTED]> added the comment:
The attached file sp-3.py simulates what I think is happening within the
subprocess module. Note that the OS handle is duplicated to allow
inheritance and then left unclosed on failure. If it is explicitly
closed, the file can be removed.
Tim Peters <[EMAIL PROTECTED]> added the comment:
This isn't "a bug", since it's functioning as documented and designed.
Read note 1 in the "date Objects" section of the reference manual,
explaining the meaning of "date2 = date1 + timedelta":
"
New submission from Tim Golden <[EMAIL PROTECTED]>:
The following code raises an Assertion Failure under debug in r64518
running on Windows XP SP2:
import ctypes
class X (ctypes.Structure): pass
ctypes.POINTER (X)
Assertion failed: PyErr_Occurred(), file ..\Modules\_ctypes\_ctypes.c
Tim Golden <[EMAIL PROTECTED]> added the comment:
The comment just before _ctypes.c:309 indicates that when a NULL is
returned at that point, an error condition should already obtain.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Tim Peters <[EMAIL PROTECTED]> added the comment:
If you think using 16 (when possible) will stop complaints, think again
;-) For example,
>>> for x in 0.07, 0.56:
... putatively_improved_repr = "%.16g" % x
... assert float(putatively_improved
Tim Peters <[EMAIL PROTECTED]> added the comment:
The error message is correct. In the Gregorian calendar, years
divisible by 100 are not leap years, unless they're also divisible by
400. So 2000, 2400, 2800, ..., are leap years, but 2100, 2200, 2300,
2500, 2600, 2700, 2900, ... a
Tim Peters <[EMAIL PROTECTED]> added the comment:
About (2**52-1)*2.**(-1074): same outcome under Cygwin 2.5.1, which is
presumably based on David Gay's "perfect rounding" code. Cool ;-)
Under the native Windows 2.5.1:
>>> x = (2**52-1)*2.**(-1074)
>>>
Tim Peters <[EMAIL PROTECTED]> added the comment:
I'm afraid you missed the joke ;-) While you believe spaces are
required on both sides of an em dash, there is no consensus on this
point. For example, most (but not all) American authorities say /no/
spaces should be used. That
Tim Peters <[EMAIL PROTECTED]> added the comment:
Mark, I don't currently have a machine with SVN and a compiler
installed, so can't play with patches. I just want to note here that,
if you're concerned about speed, it would probably pay to eliminate all
library call
Tim Peters <[EMAIL PROTECTED]> added the comment:
Mark, changing API is something to avoid after beta cycles begin (so,
e.g., it's late in the game to /add/ a new API, like a new method for
complex summation). But there's no particular reason to fear changing
implementation f
Tim Peters <[EMAIL PROTECTED]> added the comment:
I doubt this is a bug in Python. It's more likely an error (one or more
;-)) in the logic of the script, triggered by the inherently
unpredictable order of set iteration.
Some evidence: I added a `.counter` member to the Sequence
Tim Peters <[EMAIL PROTECTED]> added the comment:
Vadim, to see how memory addresses change, simply add something like
print "id", id(self)
to Sequence.__init__. On Windows (Vista, Python 2.5.1), I see different
addresses printed each time the program is run. Then, as
Changes by Tim Wegener <[EMAIL PROTECTED]>:
--
nosy: +twegener
versions: +Python 2.5
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
New submission from Tim Maxwell <[EMAIL PROTECTED]>:
Steps to reproduce:
Python 2.5.2 (r252:60911, Feb 22 2008, 07:57:53)
[GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
Type "help", "copyright", "credits" or "license" for more informa
New submission from Tim Hemming <[EMAIL PROTECTED]>:
The following line is referencing a variable "d", but it should be "dict":
logging.warning("Protocol problem: %s", "connection reset", extra=d)
Page:- http://www.python.org/doc/2.5/lib/module-l
Tim Peters <[EMAIL PROTECTED]> added the comment:
As the doctest docs say,
Examples containing both expected output and an exception
are not supported. Trying to guess where one ends and
the other begins is too error-prone, and that also makes
for a confusing test.
Sinc
Tim Peters <[EMAIL PROTECTED]> added the comment:
> Anything in obmalloc that is not arena space should continue to come
> from malloc, I believe.
Sorry, but I don't understand why arena space should be different. If a
platform's libc implementers think mmap should b
Tim Peters <[EMAIL PROTECTED]> added the comment:
I have to admit that if Python /didn't/ know better than platform libc
implementers in some cases, there would be no point to having obmalloc
at all :-(
What you (Martin) suggest is reason
New submission from Tim Pietzcker <[EMAIL PROTECTED]>:
I have experienced the exact same thing on two different PCs, one
running WinXP (German, 32bit Intel) SP2, one running SP3: When starting
the Python command line or when trying to run a Python script, I
immediately get the (Windows)
Tim Pietzcker <[EMAIL PROTECTED]> added the comment:
OK, thanks. I have set it to install for all users, if that's still
relevant. Is there a way to manually install the MS CRT (which version),
so I can use b3 until rc1 comes out?
Thanks,
Tim
___
Tim Pietzcker <[EMAIL PROTECTED]> added the comment:
Thanks a lot, now it works! The download link is
http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf
in case someone else needs it.
Best regards,
Tim
___
Tim Peters <[EMAIL PROTECTED]> added the comment:
No thought went into picking random.random in the test -- it was just a
random ;-) choice. Amaury's analysis of the source of non-determinism
is on target, and the easiest fix is to pick a coded-in-Python function
to pickle instead.
Tim Peters <[EMAIL PROTECTED]> added the comment:
Amaury, yes, it would be nice if pickle were more reliable here. But
that should be the topic of a different tracker issue. Despite the
Title, this issue is really about sporadic pickletools.py failures, and
the pickletools tests are try
Tim Peters <[EMAIL PROTECTED]> added the comment:
BTW, note that the Title of this issue is misleading:
pickle.whichmodule() uses object identity ("is":
if ... getattr(module, funcname, None) is func:
) to determine whether the given function object is supplied by a
modu
Tim Peters <[EMAIL PROTECTED]> added the comment:
Not a bug. Try (future - now).seconds instead so that the timedelta is
positive. As explained in the docs, a negative timedelta is normalized
so that only the .days attribute is negative, and, as the docs also say,
"normalization
Tim Gordon <[EMAIL PROTECTED]> added the comment:
By prefixing a number with 0, you're actually using octal rather than
decimal (i.e., only digits 0 to 7 are valid). For example, try:
>>> print 030
24
>>> print 077
63
patricio wrote:
> New submission
Tim Gordon <[EMAIL PROTECTED]> added the comment:
Whoops, I thought the tracker automatically removed quoted text! :z
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
New submission from Tim Delaney <[EMAIL PROTECTED]>:
If there is a directory to be copied to _static, Sphinx first attempts
to delete any directory by the same name in the _static directory. See
attached sphinx_static_exc.txt for the exception.
The simplest fix is to change the call (li
Tim Delaney <[EMAIL PROTECTED]> added the comment:
Oops - didn't complete my thought. The issue is that if the directory
does not already exist, the attached exception is raised.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.
Tim Golden added the comment:
Traceback (most recent call last):
File "", line 1, in
WindowsError: [Error 6] The handle is invalid
I suspect that .iterkeys / .itervalues would be more
acceptable spellings as those mirror the dict methods.
Whether the idea of extending _winreg
Tim Golden added the comment:
Sorry; the email interface messed that up. The code
which triggered the error was:
import _winreg
list (
_winreg.IterValue (
_winreg.OpenKey (_winreg.HKEY_CURRENT_USER, "Console")
)
)
--
Tim Golden added the comment:
Just think about it for a minute:
t = (1, 2)
print id (t), t
t += (1, 2, 3)
print id (t), t
Not mutating, merely creating a new new object
and giving it the same name
--
nosy: +tim.golden
___
Python tracker
<h
Tim Peters added the comment:
Note that nothing in obmalloc is _intended_ to be thread-safe. Almost all
Python API functions make the caller responsible for serializing calls (which
is usually accomplished "by magic" via the GIL). This includes calls to all
facilities supplied b
Tim Peters added the comment:
Amaury, I have no real idea what your "No, the description above says it: ..."
is a response to, but if it's to my point that obmalloc is not intended to be
thread-safe, it's not addressing that point. Any case in which another thread
Tim Peters added the comment:
Just noting there are ways to trick the macro into reading a thing once. For
example, embed something like a
((x = arenas[(POOL)->arenaindex].address) || 1)
clause early on & refer to x later (where x is some file-scope new variable).
obmalloc is not i
Tim Peters added the comment:
Right, I already agreed it would be fine to fix this if it's cheap ;-)
I didn't give any real thought to the macro solution, but that's fine by me
too. It would be best to embed the assignment in a _natural_ place, though;
like
Tim Peters added the comment:
> `x` should be a local variable. ... assembler code will be smaller.
??? It should make no difference to an optimizing compiler. Lifetime analysis
(even if it's feeble) should be able to determine that all uses are purely
local, with no need to store t
Tim Peters added the comment:
Whatever works best. Unsure what you mean by "global", though, because it's
not a C concept. File-scope variables in C can have internal or external
linkage; to get internal linkage, so that lifetime analysis is effective
without needing (r
Tim Peters added the comment:
Cool! Python has a long history of catering to feeble compilers too ;-), so
using function locals is fine. Speed matters more than obscurity here.
--
___
Python tracker
<http://bugs.python.org/issue8
Tim Golden added the comment:
On 31/03/2010 14:20, Michael Foord wrote:
> - TESTFN
>
> This is a global for setting the directory temporary files are created in?
> Don't think I like the global approach. Which functions is it used by?
It's used *all over the place*. I
Tim Peters added the comment:
At heart, this is really the same kind of thing that eventually prodded Python
into adopting David Gay's burdensome ;-) code for correctly rounded
double<->string I/O conversions. We could similarly take on porting and
maintaining KC Ng's fdlibm
Tim Golden added the comment:
Seeing the same thing on 32-bit WinXP on x86
On 07/04/2010 14:34, Stefan Krah wrote:
>
> New submission from Stefan Krah:
>
> On Windows/amd64, I get loads of pickling errors in test_multiprocessing.
>
> Type 1 error:
>
> Tracebac
Tim Lesher added the comment:
I just hit this one myself, and was about to write a bug and patch.
On reviewing the patch:
1. This really has the same issue as the original code: it detects one of a few
known return values, and will infinitely loop on an unexpected return value.
It would be
Tim Golden added the comment:
This is basically a rerun of this discussion a couple of years ago:
http://mail.python.org/pipermail/python-dev/2008-April/078333.html
The problem certainly still happens against trunk -- I have a semi-aggressive
test-harness which can cause it to reproduce
Tim Golden added the comment:
In one window run the attached script (assumes you have pywin32 installed) with
a parameter of the directory the TESTFN file will end up in. Then run, eg,
test_zipfile in another window. For me:
c:\temp> watch_dir.py C:\work_in_progress\make-snapshots\tr
New submission from Tim Kersten :
$ python setup.py install --root=/tmp/ --prefix=/usr
running install
error: must supply either home or prefix/exec-prefix -- not both
I believe that this should work. --root and --prefix are, from what I can tell,
two unrelated options.
--
assignee
Tim Kersten added the comment:
I fail to see how these are, or at least should be mutually exclusive. Upon
reading your reply I would think that if one was to specify both a --prefix and
--root that the prefix would be relative to the --root.
i.e. --prefix changes the curront installation
Tim Kersten added the comment:
Ok, this is embarrassing. :-/
$ python setup.py install --root=/tmp/ --prefix=/usr
running install
error: must supply either home or prefix/exec-prefix -- not both
The above is not caused by specifying both --root and --prefix as I had
assumed. It was my
Tim Kersten added the comment:
Such an option would be useful indeed.
An idea, though perhaps it's overkill, would be to show the current values of
the options causing problems, specifically if they come from a config file or
environment variable.
i.e. when setup.cfg contains
Tim Golden added the comment:
I put together a trivial patch against the 2.7 trunk (basically: I added
a os.rename before the os.remove in test_support.unlink) and reran my
test harness with test_zipfile... and it still failed because, of course,
test_zipfile calls shutil.rmtree which bypasses
Tim Golden added the comment:
I'm afraid that the problem doesn't lie in the unlink: DeleteFile
succeeds. The problem is that the file is only marked for delete
until such time as the last SHARE_DELETE handle on it is closed.
Until that time, an attempt to (re)create the file for anyt
Tim Golden added the comment:
> Then we shouldn't use DeleteFile in the first place to delete the file,
> but instead CreateFile, with DELETE access (and FILE_SHARE_DELETE
> sharing). If that fails, we need to move the file to the bin
> (see unlink_nt for details).
I see what
New submission from Tim Golden :
There is a reference to _winreg left in test_winsound. Trivial patch attached
renames this to winreg.
--
components: Tests
files: test_winsound.patch
keywords: patch
messages: 103042
nosy: tim.golden
severity: normal
status: open
title: _winreg
Changes by Tim Golden :
--
nosy: +mark.dickinson
___
Python tracker
<http://bugs.python.org/issue8385>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Tim Golden :
test_pickle failing on WinXP
http://svn.python.org/projects/python/branches/py3k/Lib r80044
==
ERROR: test_unicode (__main__.CPicklerTests
Tim Golden added the comment:
Yes:
C:\temp>\work_in_progress\make-snapshots\branches
Python 3.2a0 (py3k:80030, Apr 13 2010, 11:13:13)
Type "help", "copyright", "credits" or "license"
>>> &#x
Tim Golden added the comment:
Well that's embarrassing: I updated but didn't rebuild. Sorry for the noise;
all tests passing now. Please close the call.
--
___
Python tracker
<http://bugs.python.
New submission from Tim Golden :
test_linecache in the current py3k branch is failing on my WinXP machine with
ERROR_SHARING_VIOLATION.
The attached trivial patch appears to fix the problem, altho' I'm unfamiliar
with the module in question so it may be that there's
New submission from Tim Golden :
If test_heapq is run before test_import on the current py3k head,
test_import will fail as per the attached traceback.
python -m test.regrtest -W test_heapq test_import > test_import.log
At a glance I can't see any obvious reason why test_heapq should
Changes by Tim Golden :
--
nosy: -tim.golden
___
Python tracker
<http://bugs.python.org/issue8273>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Tim Lyons :
A database created under python 2.5 cannot be opened under python 2.6. It gives
the error message "DB_RUNRECOVERY: Fatal error, run database recovery --
process-private: unable to find environment ", and a database created under
python 2.6 cannot
Tim Lyons added the comment:
On Mac OS X,I get
tim$ python
Python 2.5.5 (r255:77872, Mar 21 2010, 22:08:39)
[GCC 4.0.1 (Apple Computer, Inc. build 5367)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>
Tim Lyons added the comment:
I see the same slowdown in Mac OS X with python 2.6 and bsddb 4.7.3 (4.7.25).
(So, same version as Windows, and same versions as apparently run OK in linux).
I rely on MacPorts to use these products, so have no idea how I would use
bdsdb3 still less python 2.7
Tim Pietzcker added the comment:
Sorry to revive this dormant (?) topic - has anybody brought this any further?
This "feature" has tripped me up a few times, and I would be all for adding a
flag to enable the "split on zero-size matches" behavior, but I myself am not
comp
Tim Golden added the comment:
This is basically issue 7743 which is a combination of:
* Using the same filename for all tests in one process
* Something (TSvn / Virus Checker) having a delete-share handle
* Not renaming the file before removing it in test.support.unlink
MvL suggested a change
Tim Golden added the comment:
Sorry, typing too fast:
http://bugs.python.org/issue7443 - test.support.unlink issue on Windows
platform
at least insofar as the issue applies to Windows. I imagine that the
OS X thingis completely different
New submission from Tim Chase :
Patch to update ConfigParser.py so that the .get* methods can take an optional
parameter rather than raising exceptions. Usage:
cp = ConfigParser(...)
# ...
value = cp.get('MySection', 'MyOption', default='some default')
i
Tim Chase added the comment:
For some reason, the diff didn't attach to the previous message.
--
___
Python tracker
<http://bugs.python.org/issue8666>
___
___
Tim Chase added the comment:
Trying a 3rd time to attach the diff (this time from Safari instead of FF)
--
keywords: +patch
Added file: http://bugs.python.org/file17264/ConfigParser.diff
___
Python tracker
<http://bugs.python.org/issue8
Tim Chase added the comment:
Yes, the use-case is the same as a dict.get(key, default) which I frequently
use -- so it can be used in things like
result = some_function(
cp.get('MySection', 'MyValue', default='hello'),
cp.getint('MySection'
Tim Chase added the comment:
The "raise_on_bad" (I'm ambivalent on the name, but if you come up with a
better name, I'd be fine with changing it) allows you to differentiate between
an option that isn't provided, and one that is provided, but can't be convert
Tim Hatch added the comment:
Uploading corrected diff -- the old one missed a couple of instances of DOTLESS
I -> EURO.
--
versions: +Python 2.7
Added file: http://bugs.python.org/file17301/cp858.diff
___
Python tracker
<http://bugs.pyth
Tim Peters added the comment:
I find this whole discussion to be hilarious ;-)
"Approximate upper bound" is gibberish - "upper bound" is a crisp concept that
means what it says. It's not necessarily true that an upper bound is
inaccurate - it may be exactly r
Tim Golden added the comment:
Looks like it's the backslash as Windows path separator confusing the
sphinx.util.relative_uri function. I'll try to put a patch together,
although I'm not sure if relative_uri should use os.sep or whether the
paths should be canonicalised before gett
Tim Golden added the comment:
Patch against sphinx r59269. Split on "/" and local os.sep. Causes
problems with sphinx-web under native Win32.
Added file: http://bugs.python.org/file8853/sphinx-r59269.patch
__
Tracker <[EMAIL PROTECTED]>
<htt
Tim Golden added the comment:
I'm a little flummoxed. Patching relative_uri in the
sphinx/util/__init__.py to re.split on ("/" + os.sep) sorts out the
static generation. But it seems to introduce a couple of problems with
the web-server version of the docs. One is that links e
Tim Golden added the comment:
OK, hacking away a bit further, I think I've found a solution, but I'll
need to tidy it up a bit. In essence, the problem is that the "filename"
is trying to be two things: the pointer for the local filesystem, and
the uri for the web server
Tim Golden added the comment:
The attached patch against r59286 tries to tease apart the uses of
filename by adding "webify_filepath" and "unwebify_filepath" functions
to sphinx.utils which are then used throughout the app to convert from
filesystem-separated to web-separat
New submission from Tim Golden:
One typo refers to "from __future__ import generators" in the context of
the with statement.
Later what appears to be an incomplete sentence giving an example of the
__dir__ method.
The patch attached is against r59286 of doc/whatsn
New submission from Tim Golden:
The tiniest of punctuation typos in using/cmdline.rst. Patch is against
59286 of doc/using/cmdline.rst
--
components: Documentation
files: doc-using-cmdline-r59286.patch
messages: 58119
nosy: tim.golden
severity: normal
status: open
title: Tiny typo in
Changes by Tim Golden:
--
severity: normal -> minor
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1547>
__
___
Python-bugs-list mailing list
Uns
Changes by Tim Golden:
--
severity: normal -> minor
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1548>
__
___
Python-bugs-list mailing list
Uns
201 - 300 of 2346 matches
Mail list logo
