Tim Golden added the comment:
Erik Sandberg wrote:
> Erik Sandberg added the comment:
>
> I experimented further, the only way to run a .bat file whose name
> contains funny characters, seems to be:
>
> subprocess.call('""f(o.bat""', shell=Tr
Tim Golden added the comment:
Erik Sandberg wrote:
> Erik Sandberg added the comment:
>
> Did you test your code?
Several times, cutting and pasting into the Python interpreter.
But I missed the fact that you were running Python 2.5
Python 2.6.1 (r261:67517, Dec 4 2008, 16:51
New submission from Tim Cuthbertson :
This patch adds the behaviour that when a unittest.failureException is
thrown in a TestCase's tearDown method, the test case is added to the
failures list (instead of the errors list, and only when the test case
body has passed successfully).
In
Tim Cuthbertson added the comment:
updated patch: made the test method name unique (oops), and added the
specific test case where both test body and tearDown raise failure
exceptions. This patch supercedes the original (v0)
--
Added file: http://bugs.python.org/file13388/unittest-fail
Tim Cuthbertson added the comment:
I agree that this is not normally the point of tearDown methods.
However, allowing it reduces repetition when you want to verify that
some invariant is not violated by any test.
I also think that as far as the test writer is concerned, an assertion
error is a
Tim Cuthbertson added the comment:
In my mind, an error means something is wrong. A failure just means a
test case hasn't been implemented yet, or has regressed. For me it's
misleading to have an AssertionError reported as a failure. It's not as
if changing the reporting in this
Tim Peters added the comment:
The CPython set/dict implementation does not guarantee "minimal constant
density", so "quite easy" doesn't apply in reality. For example, a set
that once contained a million elements may still contain a million
/slots/ for elements
Tim Peters added the comment:
The CPython set/dict implementation does not guarantee "minimal constant
density", so "quite easy" doesn't apply in reality. For example, a set
that once contained a million elements may still contain a million
/slots/ for elements
Changes by Tim Peters :
--
___
Python tracker
<http://bugs.python.org/issue1551113>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/m
Tim Golden added the comment:
Can I nudge this one a bit? It causes an interpreter crash and the patch
seems good (subject to someone else's review).
--
___
Python tracker
<http://bugs.python.org/i
Tim Lesher added the comment:
Thanks, Antoine. I will re-check the patch against trunk and add tests
this week.
--
___
Python tracker
<http://bugs.python.org/issue1674
New submission from Tim Driscoll :
These are supposed to raise a unittest.SkipTest on win32 but the
unittest import is missing. The patch just adds the missing import
See patch here:
http://codereview.appspot.com/32074/show
--
components: Tests
messages: 84607
nosy: brett.cannon
New submission from Tim Driscoll :
The patch and test is here:
http://codereview.appspot.com/28161/show
There were no tests so i added a few of them. The one that breaks
without the patch to timeit is:
test_setup_is_called_when_the_statment_is_string_and_the_setup_is_not()
(sorry for the long
Changes by Tim Driscoll :
--
title: timeit breaks when the statment is a string and the setup is not -> fix
for timeit when the statment is a string and the setup is not (and tests)
___
Python tracker
<http://bugs.python.org/iss
Tim Mooney added the comment:
Solaris has both traditional System V curses and an XPG4-compatible
curses that does include mvwchgat. The traditional system V curses is
the default, for backward compatibility.
If you want the XPG4 compatible curses, you need to make sure
-I/usr/xpg4/include
Tim Golden added the comment:
Is there mileage for glob.glob to grow a dialect
param, with a default value to keep it backwards
compatible? Otherwise, presumably, proponents of
some other xsh variant will come forward with
their scheme of matching, and regex-followers
with theirs and so on
Tim Wegener added the comment:
I encountered this bug at my previous place of employment. I've since
moved on, so I don't have access to the code/setup where this originally
occurred.
I tried to setup a test case to reproduce this, but was thwarted by
another bug, probably related t
Tim Golden added the comment:
Well it may be uncommon, but it's perfectly easily reproducible:
Just try to reinstall / repair from a file not called
python-2.5.2.msi. Maybe uninstall: haven't tried.
If Martin doesn't get there, I'll try to look at the log and
see
New submission from Tim Golden :
tools/msi/msi.py is still trying to copy the README file from the
lib/test directory. This file was removed in r70872. Patch attached
against r71393 of msi.py.
--
components: Build, Demos and Tools, Windows
files: msi.r71393.patch
keywords: patch
Tim Golden added the comment:
Edmund Eyles wrote:
> New submission from Edmund Eyles :
>
> The documentation for the webbrowser module at
> http://www.python.org/doc/2.5/lib/module-webbrowser.html refers to the
> use of the BROWSER environment variable as a means to control whi
Index: bdist_msi.py
===
--- bdist_msi.py(revision 72507)
+++ bdist_msi.py(working copy)
@@ -141,6 +141,8 @@
bdist_base = self.get_finalized_command('bdist').bdist_base
self.bdist_dir = os.path.
Changes by Tim Golden :
--
assignee: -> tarek
components: +Distutils
nosy: +tarek
type: -> behavior
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/
New submission from Tim Savannah :
I'm getting many segmentation faults (about 1 per half hour) from within
the core of python 2.6.2 on 64-bit machines.
(examples from dmesg:
pythonLaunch.py[13307]: segfault at 0058 rip
2b845cfb3550 rsp 41809930 error 4
pythonLaun
Tim Savannah added the comment:
Yes I compiled python myself, using ./configure
--prefix=/usr/local/python2.6/ --with-pth --enable-shared
It is a 64-bit compile.
I've done this with both standard config and a config that I modded
which produces optimizations options as -ggdb3 -O0.
Tim Savannah added the comment:
All site-packages were compiled against python 2.6.1, and python was
upgraded later to 2.6.2 (but upon running a make install with python
2.6.2, it seemed to recompile site-packages on a byte-code level).
And no, there is still segfaults without optimizations
Tim Savannah added the comment:
recompiled with pydebug enabled, and recompiled all site-packages. Still
getting exceptions, however they are occuring within the python binary
now and not libpython2.6.1 .
pythonLaunch.py[25914]: segfault at 0068 rip
004c7694 rsp
Tim Savannah added the comment:
to update, no additional output was seen from pydebug.
--
___
Python tracker
<http://bugs.python.org/issue6178>
___
___
Python-bug
Tim Peters added the comment:
> Out of interest, what does '%#.0f' % 1.5 produce on
> Python 2.7/Windows?
Microsoft's float->string routines have always done "add a half and
chop" rounding. So, yes, 1.5 rounds to 2 there.
> ...
> I suspect that we&
Tim Golden added the comment:
I doubt there's any real likelihood of the official Python 2.5.4 being
generated with a different compiler: it would mean, in principle, that all
binary extensions would have be recompiled to ensure there were no issues. I
suggest you ask on the Python ma
Tim Golden added the comment:
Eric Smith wrote:
> Eric Smith added the comment:
>
>> So is this a cosmetic issue or a functional issue?
>
> It's a cosmetic issue.
>
>> Also, even if it could figure that out, how would it know whether
>> a part
Tim Golden added the comment:
What's superior about .tar.gz? (This is a genuine question).
--
nosy: +tim.golden
title: Native (and default) tarfile support for setup.py sdist in distutils on
Windows -> Native (and default) tarfile support for setup.py sdist in
dist
New submission from Tim Mooney :
I've built Python 2.6.1 and Python 2.6.2 on x86_64-sun-solaris2.10 using
the Sun Workshop Express (200903) toolchain. I'm building in 64 bit mode.
Most stuff builds just fine (even warnings are rare), but pyexpat fails
to link with this error:
Tim Golden added the comment:
Making something executable on Windows has nothing to
do with file permissions. You can set them as much
as you like, but executability is determined by file
associations, possibly in association with PATHEXT
settings. AFAICT, the current Python installer does
this
Tim Golden added the comment:
Attached is a patch against r73685 of the documentation for subprocess
which adds some information about using shell=True on Windows. I plan
to do some more general-purpose docs for subprocess on Windows, but as
I've failed to get round to them for a year
Tim Peters added the comment:
Do you realize that 2**54-1 isn't exactly representable as a float? It
requires 54 bits of precision, but the Python float format only has 53
bits available (on all popular boxes).
>>> 2**54-1
18014398509481983L
>>> float(_) # rounds t
Tim Peters added the comment:
Yup, -1 here too. For dyadic arithmetic operations (+ - * / % //) on
mixed numeric types, Python's execution model coerces the operands to a
common type before computation begins. Besides just being the way it's
worked "forever" in Python,
Tim Peters added the comment:
Terry asks:
> is it also guaranteed that quick_ratio() <= real_quick_ratio()
Nope! The docs don't say that, so it's not guaranteed.
It's not the _intent_ of the code that it be true, either. The only point to
quick_ratio() and real_q
Tim Hatch added the comment:
I also noticed that libforensics supplies a codec for cp858, if that's helpful
to double-check the implementation.
http://code.google.com/p/libforensics/source/browse/code/lf/win/codepage/cp858.py
--
___
Python tr
Tim Golden added the comment:
Since execfile is basically shorthand for exec (open (filename).read ()),
and since open (filename) *does* support the full range of filepath
syntax on Windows, and since execfile has been removed in py3k in favour
of exec (open ...)), and since Python 2.x is
Tim Golden added the comment:
I'm unlikely to get to it soon. If there's no urgency I can
look at it later. FWIW, it's not something I'm especially
familiar with.
On 12/06/2010 01:02, STINNER Victor wrote:
>
> STINNER Victor added the comment:
>
> Tim: are you
New submission from Tim Golden :
The reference to PyDateTime_IMPORT in the C API datetime docs is marked
up as cfunction, giving it a pair of brackets which render it invalid.
There is also no indication of where in the code it should be invoked.
Patch attached.
--
files
Changes by Tim Golden :
--
assignee: -> d...@python
components: +Documentation
nosy: +d...@python
stage: -> patch review
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/
Tim Golden added the comment:
Switching to Python 3.2 as this essentially constitutes a behaviour change and
2.6 is in bugfix mode and 2.7 is about to enter rc2. It would certainly be
possible to use one of the volume APIs under the covers. Would you be willing
to offer a patch to, say
Tim Golden added the comment:
All we need to do is check the FILE_ATTRIBUTE_REPARSE_POINT
in the file attributes. Frustratingly, we grab file attributes
a dozen times in posixpath.c only to throw most of it away.
Is there a case for adding an "attributes" function to os.path
which e
Tim Golden added the comment:
... of course you still need to get the reparse tag to determine whether this
is a mount point so the file attributes alone in this case are not enough.
--
___
Python tracker
<http://bugs.python.org/issue9
Changes by Tim Golden :
--
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8869>
___
___
Python-bugs-list
Tim Golden added the comment:
Error no longer occurs
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Tim Golden added the comment:
I think we're saying the same thing :)
The simplest thing to do here is to create a win_ismount function
in posixmodule.c which does the attributes / reparse tag dance and
returns True/False and use that wherever it's needed to support this
concept und
Tim Peters added the comment:
> It would be great if you could shed
> some light on the history behind pure
> python implementation. Why was it
> developed in the first place?
It was rapid prototyping - design decisions were changing daily, and it goes a
lot faster to change Pyth
Tim Peters added the comment:
> What would be your opinion on adding
> datetime.py to the main python tree
> today?
The funny thing is I can't remember why we bothered creating the C version - I
would have been happiest leaving it all in Python.
Provided the test suite ensure
Tim Golden added the comment:
That's (still...) a known issue with Windows file associations and
redirects:
http://support.microsoft.com/kb/321788
In theory it was fixed way back when. In practise...
On 30/06/2010 15:04, Vojtech Fried wrote:
>
> Vojtech Fried added the com
Tim Peters added the comment:
> I thought x was coming from integer
> arithmetics, but apparently datetime.py loves floats!
The arguments to __new__ can be floats, so it's necessary to deal with floats
there.
--
___
Python tra
Tim Peters added the comment:
> I thought x was coming from integer
> arithmetics, but apparently datetime.py loves floats!
The arguments to __new__ can be floats, so it's necessary to deal with floats
there.
--
___
Python tra
Changes by Tim Peters :
--
___
Python tracker
<http://bugs.python.org/issue7989>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/m
Tim Peters added the comment:
> Do you remember why it was a good idea to
> derive datetime from date?
Why not? A datetime is a date, but with additional behavior. Makes
inheritance conceptually natural.
--
___
Python tracker
Tim Peters added the comment:
I'm not going to argue about whether datetime "should have been" subclassed
from date - fact is that it was, and since it was Guido's idea from the start,
he wouldn't change it now even if his time machin
Tim Peters added the comment:
> ...
> Another is tzinfo attribute of time. With time t,
> t.utcoffset() is kid of useless given that you
> cannot subtract it from t
Sure you can - but you have to write your code to do time arithmetic. The time
implementation does so under the cov
Tim Golden added the comment:
Although I'm the implementer of the patch (the concept
was discussed way back on c.l.py after a naive poster's
original request) I'm probably +0 myself. It's an attempt
to replace os.access' next-to-useless behaviour on Windows
with some
Tim Lesher added the comment:
There are a number of similar mentions in the C API docs and index; attached is
a patch that removes each.
--
keywords: +patch
nosy: +tlesher
Added file: http://bugs.python.org/file18068/remove-extraneous-types.diff
Tim Peters added the comment:
FYI, I like the change. As I recall it, the current wording was just to avoid
saying "ahead of UTC" or "behind UTC" (which was the original wording).
Technically pure or not, I never saw anyone get truly confused by "East of UTC"
Tim Lesher added the comment:
It looks as if this has been addressed for list.index (aka issue #7252), in
r76058. The same fix could be applied for list.remove.
--
___
Python tracker
<http://bugs.python.org/issue4
Tim Lesher added the comment:
Added patch that replicates the change in r82035 for Visual Studio 2005 (VC8)
builds.
--
nosy: +tlesher
Added file: http://bugs.python.org/file18107/add_time_to_vc8_build.diff
___
Python tracker
<h
Tim Lesher added the comment:
This patch combines the fix from Georg Brandl's original patch with the fix
made to listindex. The r76058 fix fails the test in Georg's original test
where the repr of the item to be removed itself raises; this patch handles that
case for both list.
Tim Lesher added the comment:
This appears to run afoul of Microsoft's "security-enhanced CRT", which aborts
a program that calls certain API functions (including signal) with invalid
parameters.
PyOS_getsig() has conditionally-compiled code added to deal with this (and
Tim Lesher added the comment:
No, there's no automated way to keep "legacy" Windows toolchains in sync; short
of adopting something like Scons or CMAKE (which I'm *not* suggesting) I don't
think I've seen a trustworthy way of doing so.
The PCBuild's "
Changes by Tim Lesher :
Removed file: http://bugs.python.org/file18107/add_time_to_vc8_build.diff
___
Python tracker
<http://bugs.python.org/issue9012>
___
___
Python-bug
Changes by Tim Lesher :
Added file: http://bugs.python.org/file18113/add_time_to_vc8_build.diff
___
Python tracker
<http://bugs.python.org/issue9012>
___
___
Python-bug
Tim Lesher added the comment:
Ugh. That's a reasonable objection.
What's the best thing to do in this case, generally speaking?
list.index() does print the full repr on a value error; and a quick grep shows
a number of other similar uses, although those don't seem to be as e
Tim Golden added the comment:
Not necessarily; pyreadline takes over from the standard console
functionality on Windows in order to emulate a more Unix-ish
approach. I prefer the Windows default.
There's nothing to stop someone downloading and installing
pyreadline as a third-party packa
Changes by Tim Golden :
--
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue6040>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Tim Golden :
--
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue4453>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Tim Golden :
--
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue9503>
___
___
Python-bugs-list mailing list
Unsubscribe:
Tim Golden added the comment:
Patch attached with code & test which fixes this within _subprocess.c at least
for Windows
--
assignee: -> tim.golden
Added file: http://bugs.python.org/file18398/3210.r83741.patch
___
Python tracker
Tim Golden added the comment:
Patch added for 31 branch
--
Added file: http://bugs.python.org/file18399/3210.release31-maint.patch
___
Python tracker
<http://bugs.python.org/issue3
Tim Golden added the comment:
Patch added for 27 branch
--
Added file: http://bugs.python.org/file18400/3210.release27-maint.patch
___
Python tracker
<http://bugs.python.org/issue3
Tim Golden added the comment:
Brian, I'm not sure that the test as rewritten will exercise the error.
The key is that the traceback object will prevent the handles
from being finalised until it is itself finalised. After your
change I expect the handles to release anyway since the traceba
Tim Golden added the comment:
Committed in r83759 r83760 r83761
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Changes by Tim Golden :
--
assignee: -> tim.golden
___
Python tracker
<http://bugs.python.org/issue7443>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Tim Golden :
--
assignee: -> tim.golden
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue4708>
___
___
Python-bugs-list mai
Changes by Tim Golden :
--
assignee: -> tim.golden
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue1714451>
___
___
Python-bugs-list mai
Changes by Tim Golden :
--
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue1681974>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Tim Golden :
--
assignee: -> tim.golden
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue1672853>
___
___
Python-bugs-list mai
Changes by Tim Golden :
--
assignee: -> tim.golden
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue1707753>
___
___
Python-bugs-list mai
Changes by Tim Golden :
--
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue1142>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Tim Golden :
--
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue6609>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Tim Golden :
--
assignee: -> tim.golden
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue6839>
___
___
Python-bugs-list mai
Changes by Tim Golden :
--
assignee: -> tim.golden
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue8006>
___
___
Python-bugs-list mai
Changes by Tim Golden :
--
assignee: -> tim.golden
components: +Windows
___
Python tracker
<http://bugs.python.org/issue2304>
___
___
Python-bugs-list mai
Tim Golden added the comment:
Blast. Thanks; I'll have to rework those patches then.
--
status: closed -> open
___
Python tracker
<http://bugs.python.or
Tim Golden added the comment:
If individual users want to change these around, it's easy enough to do so
post-hoc. Closing as won't fix.
--
nosy: +tim.golden
resolution: -> wont fix
___
Python tracker
<http://bugs.python.
Changes by Tim Golden :
--
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1566260>
___
___
Python-bugs-
Tim Golden added the comment:
OK, the issue identified by Hirokazu Yamamoto in msg113106 only actually
affects the 2.x series, because of the awkwardly multiple-level interaction
between file handles. The io rewrite in 3.x seems not to suffer the same way.
Nonetheless, the proposed
Tim Golden added the comment:
Committed in r83815, r83816, r83817
--
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Tim Golden added the comment:
Committed as r83830, r83831, r83832
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
Tim Golden added the comment:
Duplicate of #2304
--
resolution: -> duplicate
status: open -> closed
___
Python tracker
<http://bugs.python.org/iss
Tim Golden added the comment:
I can't reproduce on W7. Strangely, though, although my banner suggests that I
have exactly the same build as you, I get a "\r\n" at the end of the
communicate bytestream, not a simple "\n" as you're getting. Do you have any
e
Tim Golden added the comment:
I've just run this:
import os
fd = os.popen("cat.exe", "w")
for i in range (100):
_ = fd.write ("%d\n" % i)
fd.flush ()
and seen the expected list of numbers on the screen. cat.exe is from the
gnuwin32 tools but I'm
Tim Golden added the comment:
To confirm the situation on 3.x: a unicode string with non-ascii-encodable
characters is fine. The easy test here in the uk is a pound sign:
import subprocess
FILENAME = "abc£.bat"
FILENAME.encode ("ascii")
#
# UnicodeEncodeError
#
with ope
Tim Golden added the comment:
OK, I'm going to close this one:
* commands is out of 3.x
* it's a convenience for 2.x anyway, not a showstopper
If anyone feels keen enough to reopen the request, I'm willing to commit a
suitable patch against the release27-maint branch, but I
Tim Peters added the comment:
I stopped understanding doctest the last time it was rewritten - it got far
more generalized than I ever intended already. It's up to the younger
generation to decide how much more inscrutable to make i
1901 - 2000 of 2346 matches
Mail list logo