Changes by Brian Curtin :
--
priority: -> low
resolution: -> rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue7756>
___
Changes by Brian Curtin :
--
priority: -> normal
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue7760>
___
___
Python-bugs-list
Changes by Brian Curtin :
--
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
type: -> behavior
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
--
priority: -> normal
stage: -> test needed
status: open -> pending
versions: +Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.o
New submission from Brian Curtin :
I always find myself wishing sys.getwindowsversion() utilized the named tuple
concept, so here it is against trunk. sys.version_info was also changed in this
manner for 2.7.
Because it is a PyStructSeq/named tuple, it is still accessible like a regular
old
Brian Curtin added the comment:
Good point about OSVERSIONINFOEX. I've actually wanted some of that info as
well, and according to MSDN the minimum supported client to get that structure
is Windows 2000 - same as OSVERSIONINFO.
Attached is a patch updated with your comments plus the u
Changes by Brian Curtin :
--
components: +Interpreter Core -Extension Modules
keywords: +needs review
priority: -> normal
stage: -> patch review
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/
Brian Curtin added the comment:
After thinking about this, I don't see a need for any change.
Although it _looks_ like the relpath implementations aren't compatible based on
their start default parameters, they do work the same. My code change isn't
really necessary.
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue3754>
___
__
Brian Curtin added the comment:
Can you submit your patch as a unified diff -- it's not easy to tell where you
made changes to that file.
Can you also include tests showing how this is used, especially using
register_function in both the old way and the new way you propose?
Lib
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue3871>
___
__
Brian Curtin added the comment:
http://www.python.org/dev/workflow/ and http://python.org/dev/faq/ should help
you get started. The workflow doc will let you know what the process is around
here. The FAQ will tell you how to setup Subversion, how to make a diff, etc.
With that said, I think
Brian Curtin added the comment:
Once you get a Subversion checkout of the source, have a look in
Lib/test/test_xmlrpc.py for examples of how things are currently tested (using
unittest). Once you get a feel for it, add new tests for what your changes do.
The file you paste'd looks good
Brian Curtin added the comment:
After looking into this again, the testing situations are much different than I
had originally written.
Some of the tests aren't really valid exercises. For one, the
querying/enabling/disabling of reflection keys aren't good tests as they aren
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> patch review
type: -> behavior
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
--
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
versions: +Python 2.7, Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
nosy: +brian.curtin
priority: -> normal
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue>
___
___
Brian Curtin added the comment:
Another one-liner, stopTestRun
--
nosy: +brian.curtin
Added file: http://bugs.python.org/file16002/stopTestRun.diff
___
Python tracker
<http://bugs.python.org/issue7
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue4440>
___
__
Brian Curtin added the comment:
Thanks a lot for taking a look at this, Eric and Marc-Andre. Apologies for the
few mistakes in there, I jumped the gun and submitted that last patch before
having run the full test suite again.
Good catch on the missing #ifdef. I will also run this on Mac and
Changes by Brian Curtin :
--
components: +Library (Lib) -2to3 (2.x to 3.0 conversion tool)
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/
Brian Curtin added the comment:
unittest also does this, but it does so at the top and references projects as a
whole, rather than individual functions/classes in the project.
Seems like this should be taken out. It doesn't exist in any version after 2.6.
--
nosy: +brian.c
Brian Curtin added the comment:
Duplicate of #6056.
--
nosy: +brian.curtin
priority: -> normal
resolution: -> duplicate
status: open -> closed
type: crash -> behavior
___
Python tracker
<http://bugs.pytho
Changes by Brian Curtin :
--
priority: -> normal
stage: -> needs patch
versions: +Python 2.7, Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue4944>
___
___
Brian Curtin added the comment:
These tests have been disabled for a little over two years now. I've run the
previously disabled tests on Windows, Mac OSX, and Linux numerous times and
haven't seen any instability or failures (not that it proves much).
I wasn't around at t
Changes by Brian Curtin :
--
stage: -> test needed
versions: +Python 2.7, Python 3.2 -Python 2.6
___
Python tracker
<http://bugs.python.org/issue1926>
___
_
Changes by Brian Curtin :
--
stage: -> test needed
versions: +Python 2.6 -Python 2.5
___
Python tracker
<http://bugs.python.org/issue2052>
___
___
Python-
Changes by Brian Curtin :
--
stage: -> test needed
versions: -Python 2.5
___
Python tracker
<http://bugs.python.org/issue1927>
___
___
Python-bugs-list mai
Brian Curtin added the comment:
Florent is correct. The patch seems to fix regular popen, but popen3 sees
problems. I'll see if I can fit this in and have a look.
Also of note is that the other flavors of popen are not tested...at least not
in Lib/test/test_popen.py or Lib/test/test_
Changes by Brian Curtin :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue1926>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Curtin added the comment:
Dan, there seem to be a number of possible issues in your last two messages.
It's not clear to me what the blinking light is. What type of computer do you
have and what is the specific installer and version you tried to run?
Also, what do you mean when yo
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> test needed
type: -> behavior
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
--
nosy: +brian.curtin, michael.foord
priority: -> normal
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/
Brian Curtin added the comment:
I'm not seeing the same thing Tim sees on 2.6, or 3.1 for that matter. Looks
like this is still an issue.
--
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
versions: +Python 2.6, Python 3.1
Changes by Brian Curtin :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue7671>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Brian Curtin :
--
components: -2to3 (2.x to 3.0 conversion tool)
stage: -> patch review
type: -> behavior
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue7826>
___
__
Changes by Brian Curtin :
--
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue7827>
___
___
Python-bugs-list
Brian Curtin added the comment:
The patch intentionally doesn't use assertIsInstance because that method
doesn't exist in 2.6.
--
___
Python tracker
<http://bugs.python.
Changes by Brian Curtin :
--
components: +Windows
keywords: +needs review
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
type: -> behavior
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
Removed file: http://bugs.python.org/file15665/issue4772.diff
___
Python tracker
<http://bugs.python.org/issue4772>
___
___
Python-bugs-list m
Brian Curtin added the comment:
Minor change to the patch to correct for Antoine's suggestion.
--
Added file: http://bugs.python.org/file16089/issue4772.diff
___
Python tracker
<http://bugs.python.org/i
Changes by Brian Curtin :
Removed file: http://bugs.python.org/file16089/issue4772.diff
___
Python tracker
<http://bugs.python.org/issue4772>
___
___
Python-bugs-list m
Changes by Brian Curtin :
Added file: http://bugs.python.org/file16090/issue4772.diff
___
Python tracker
<http://bugs.python.org/issue4772>
___
___
Python-bugs-list mailin
Brian Curtin added the comment:
I haven't yet had a chance to look into what caused the failures, but
test_tarfile did not pass. This is on Windows 7 x64.
==
ERROR: test_extract_hardlink (__main__.MiscRea
Brian Curtin added the comment:
Most of the guts have already been reviewed, but here are some mainly minor
comments on the last patch.
Lib/test/symlink_support.py
- No need to import print_function
- I'd just put the docstrings on one line
- A bunch of if tests are one-lined
Lib
Brian Curtin added the comment:
The raw_input() doesn't provide anything. I'd just drop that and pass the
string directly to shlex.split.
"Do not put an argument-taking option together with its argument as a single
item in the *args* list"
-- Something like "Argum
Changes by Brian Curtin :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue7316>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue5099>
___
__
New submission from Brian Curtin :
On Windows, the subprocess module makes use of functions publicly exposed by
PC/_subprocess.c to interact with Win32 API functions. However, no
documentation exists for these functions, neither in the online docs nor in
docstrings.
--
assignee
Brian Curtin added the comment:
Attached is a patch which adds docstrings to the functions in PC/_subprocess.c,
documents the functions in Doc/library/subprocess.rst, and removes a chunk of
unneeded import code from Lib/subprocess.py
--
keywords: +needs review, patch
stage: needs
Changes by Brian Curtin :
Removed file: http://bugs.python.org/file16110/issue7838.diff
___
Python tracker
<http://bugs.python.org/issue7838>
___
___
Python-bugs-list m
Changes by Brian Curtin :
Added file: http://bugs.python.org/file16111/issue7838.diff
___
Python tracker
<http://bugs.python.org/issue7838>
___
___
Python-bugs-list mailin
Brian Curtin added the comment:
True. Is there value in eventually privatizing these functions?
It feels weird having them exposed but not documented at all...maybe just keep
the docstrings around?
--
status: open -> pending
___
Python trac
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> test needed
type: -> behavior
versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2 -Python 2.5
___
Python tracker
<http://bugs.python.o
Brian Curtin added the comment:
Here's a patch which keeps docstrings, and explicitly qualifies the Windows
specific functions from _subprocess rather than using import * (which causes a
couple of lines just over 79 chars). Now the functions are more hidden than
before.
Ran the tests
Brian Curtin added the comment:
I just saw this today while installing the 3.1.1 final MSI on a Server 2003 box.
--
components: +Windows
nosy: +brian.curtin
priority: -> high
stage: -> needs patch
type: compile error -> behavior
___
Pytho
Changes by Brian Curtin :
--
___
Python tracker
<http://bugs.python.org/issue7854>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/m
Brian Curtin added the comment:
Rather than calling QueryValue and using fail(...) if it doesn't throw,
assertRaises(...) would do the trick.
--
assignee: theller ->
keywords: +needs review
nosy: +brian.curtin, michael.foord
priority: -> normal
stage: ->
New submission from Brian Curtin :
When running 32-bit Python on a 64-bit version of Windows, therefore running
the process in WOW64 mode, platform.machine returns a misleading value. When
running in WOW64, the processor architecture is masked to appear as "x86" when
the machine i
Changes by Brian Curtin :
Removed file: http://bugs.python.org/file15960/issue4722.diff
___
Python tracker
<http://bugs.python.org/issue4722>
___
___
Python-bugs-list m
Brian Curtin added the comment:
Note that this will also need the Workstation check that 6.0 has right above
this, because both Windows 7 and Windows Server 2008 R2 are version 6.1.x.
Also of note is that sys.getwindowsversion (renamed as GetVersionEx here) has
been expanded to make use of
Brian Curtin added the comment:
Here's a patch which fixes this on trunk.
2.6/3.1 is a different story as there doesn't appear to be a way to get the
platform type to differentiate workstation/server. #7766 is what makes it easy
on trunk, but it's a new feature and i
Brian Curtin added the comment:
This needs #7860 for properly figuring out the machine architecture for some
32-bit Python on 64-bit Windows tests.
--
dependencies: +32-bit Python on 64-bit Windows reports incorrect architecture
___
Python tracker
Brian Curtin added the comment:
Attached is what I believe is the complete patch. You'll need to apply the
patch on #7860 for proper test coverage of a 32-bit Python running on 64-bit
Windows.
Here's a summary of what's contained:
1. Documented and tested the previously u
Changes by Brian Curtin :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue7867>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Brian Curtin :
Removed file: http://bugs.python.org/file15889/issue7301.diff
___
Python tracker
<http://bugs.python.org/issue7301>
___
___
Python-bugs-list m
Brian Curtin added the comment:
Updated patch, tests weren't working.
--
Added file: http://bugs.python.org/file16157/issue7301.diff
___
Python tracker
<http://bugs.python.org/i
Changes by Brian Curtin :
--
components: +Library (Lib) -2to3 (2.x to 3.0 conversion tool)
nosy: +vinay.sajip
priority: -> normal
stage: -> test needed
versions: +Python 3.1 -Python 2.5
___
Python tracker
<http://bugs.python.org/
New submission from Brian Curtin :
While EnumKey and EnumValue directly implement the underlying Windows calls of
the same name, they don't feel very Pythonic. The user has to create their own
loop and increment a counter to get all of the keys or values, stopping the
loop when Windows
Changes by Brian Curtin :
--
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue5802>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Brian Curtin :
--
priority: -> normal
stage: -> test needed
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue7884>
___
___
Brian Curtin added the comment:
Is the situation any different if you install Python to "C:\Program Files"?
This seems to be at least part of the reason IronPython installs to "C:\Program
Files", which was discussed on the IronPython list [1] a few mon
Brian Curtin added the comment:
That change works for me.
--
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/
Brian Curtin added the comment:
Interesting, I'll take a look and see why that's happening.
Good point about the names.
--
___
Python tracker
<http://bugs.python.
Brian Curtin added the comment:
With the latest patch I get one failure: test_bufio. I piped that test to a
file and attached the results here. There are numerous "Permission denied:
@test" IOErrors.
--
Added file: http://bugs.python.org/file16181/test_bufio.
Brian Curtin added the comment:
Yep, that's the only one failing. The output I attached is the result of
running the test alone.
--
___
Python tracker
<http://bugs.python.org/i
Brian Curtin added the comment:
I don't think altzone was incorrect, but it could also use a little rewording.
Attached is a patch which rewords daylight and altzone. Thoughts?
--
keywords: +needs review
priority: -> normal
stage: -> patch review
versions: -Python 2.4,
Changes by Brian Curtin :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue3771>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Brian Curtin :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue4713>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Brian Curtin :
--
priority: -> normal
type: crash -> behavior
versions: +Python 3.1, Python 3.2 -Python 3.0
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
priority: -> normal
stage: -> test needed
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue4891>
___
___
Changes by Brian Curtin :
--
priority: -> normal
stage: -> test needed
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue6815>
___
___
Changes by Brian Curtin :
--
priority: -> normal
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue5223>
___
___
Python-bugs-list
Changes by Brian Curtin :
--
priority: -> normal
stage: -> needs patch
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue5527>
___
___
Changes by Brian Curtin :
--
priority: -> normal
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue4918>
___
___
Python-bugs-list
Changes by Brian Curtin :
--
priority: -> normal
stage: -> patch review
type: crash -> behavior
versions: +Python 3.2 -Python 2.5, Python 3.0
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue6470>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Brian Curtin :
--
priority: -> normal
type: crash -> behavior
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.4, Python 2.5
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue6668>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Brian Curtin :
--
priority: -> normal
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue6863>
___
___
Python-bugs-list
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> patch review
type: crash -> behavior
___
Python tracker
<http://bugs.python.o
Brian Curtin added the comment:
What is the output of your example? I'm not on Linux at the moment, but I'm
trying to see if this is actually a crash.
--
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
versio
Changes by Brian Curtin :
--
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue6895>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Brian Curtin :
--
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue7424>
___
___
Python-bugs-list
Brian Curtin added the comment:
The patch could use a test (which doesn't require sgmlop).
--
keywords: +needs review
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
title: Installing sgmlop can crash xmlrpclib -> Installing sgmlop causes
x
Changes by Brian Curtin :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue7893>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Brian Curtin :
--
assignee: -> ronaldoussoren
components: +Macintosh
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/iss
Brian Curtin added the comment:
With Ezio's latest patch (sent via IRC), test_bufio still fails and
additionally test_mailbox fails.
If I apply the patch on #7443 along with Ezio's patch, everything looks fine. I
haven't thoroughly looked at that issue, but on the surface i
501 - 600 of 1382 matches
Mail list logo