Changes by Brian Curtin :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue7>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Curtin added the comment:
Looks fine to me.
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue8>
___
___
Python-bugs-list mailin
Brian Curtin added the comment:
We're only a few days away from 3.2 final so it's too late. Once it goes out
I'll make the adjustment and it'll be in 3.2.1.
--
resolution: fixed ->
stage: committed/rejected -> patch revi
Changes by Brian Curtin :
--
assignee: -> bquinlan
nosy: +bquinlan
___
Python tracker
<http://bugs.python.org/issue11161>
___
___
Python-bugs-list mai
Brian Quinlan added the comment:
ProcessPoolExecutor is not expected to work with any interactive shell on
Windows because it uses the multiprocessing module behind the scenes, which has
that limitation.
I'm reclassifying this as a documentation bug since either a reference to
Brian Curtin added the comment:
A change like this would need to go through, at the least, the python-ideas
mailing list. Please submit your idea there first.
--
nosy: +brian.curtin
resolution: -> rejected
stage: -> committed/rejected
status: open -&g
Brian Curtin added the comment:
Can you confirm that the checksum and size of the file you downloaded matches
what's on the site: http://www.python.org/download/releases/2.7.1/
--
components: +Windows
nosy: +brian.curtin
___
Python tracker
Brian Curtin added the comment:
shutil.move is implemented using copy2, which as the documentation states at
the top, "On Windows, file owners, ACLs and alternate data streams are not
copied."
See http://docs.python.org/library/shutil
--
nosy: +brian.curtin
resolution: -
Changes by Brian Curtin :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue11202>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Brian Curtin :
--
nosy: -BreamoreBoy
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue7877>
___
___
Python-bugs-list m
Changes by Brian Curtin :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue11272>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Curtin added the comment:
#10841 may be related.
--
___
Python tracker
<http://bugs.python.org/issue11272>
___
___
Python-bugs-list mailing list
Unsub
Brian Curtin added the comment:
Duplicate of #11272.
--
nosy: +brian.curtin
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Brian Curtin :
--
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue6690>
___
___
Python-bugs-list mailing list
Un
Changes by Brian Curtin :
--
components: +Build
keywords: +needs review
priority: -> normal
type: -> behavior
versions: -Python 2.5
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> patch review
type: -> behavior
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue7719>
___
__
Changes by Brian Curtin :
--
keywords: +needs review
___
Python tracker
<http://bugs.python.org/issue1471934>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Curtin added the comment:
#7717 also contains code "on behalf of" other people.
--
nosy: +brian.curtin
priority: -> normal
type: -> feature request
___
Python tracker
<http://bugs.p
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> patch review
versions: -Python 2.5
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
priority: -> normal
stage: -> test needed
versions: -Python 2.5
___
Python tracker
<http://bugs.python.org/issue7713>
___
___
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue7715>
___
__
Changes by Brian Curtin :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue7712>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Curtin added the comment:
In your test, the more common convention is to use assertFalse(foo) instead of
assert_(not foo).
--
keywords: +needs review
nosy: +brian.curtin
stage: -> patch review
___
Python tracker
<http://bugs.pyth
Brian Curtin added the comment:
Most of the patch is outdated, but I could check out an updated patch on my
Win7 64 machine.
--
keywords: +needs review
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue1578
Brian Curtin added the comment:
I'm getting failures in test_glob, test_os, test_platform, test_posixpath,
test_shutil, and test_tarfile. failures.txt is attached with the results I see
on Win 7 with a 64 bit build.
I'm not seeing the exception Eric saw. That worked for me as bot
Changes by Brian Curtin :
--
nosy: +brian.curtin
stage: -> test needed
type: -> behavior
versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/iss
Brian Curtin added the comment:
Ping. Anyone know if this is still an issue? I don't have access to RH.
--
nosy: +brian.curtin
stage: -> patch review
type: -> behavior
versions: +Python 2.6 -Python 2.5
___
Python tracker
<http://b
Changes by Brian Curtin :
--
nosy: +loewis
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue7727>
___
___
Pyth
Brian Curtin added the comment:
Here's an updated version of the previous patches with the test included in
test_time.py. The test fails on Linux before the timemodule.c file is changed,
then it passes once applied.
--
keywords: +needs review
nosy: +brian.curtin
stage: -&g
Changes by Brian Curtin :
--
components: +Tests
priority: -> normal
stage: -> test needed
type: -> behavior
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
--
resolution: -> invalid
stage: -> committed/rejected
___
Python tracker
<http://bugs.python.org/issue7680>
___
___
Python-bugs-
Brian Curtin added the comment:
FWIW, Amaury's example runs without error on trunk and py3k (OS X 10.5).
2.6 prints the following:
"Exception in thread Thread-1 (most likely raised during interpreter shutdown)"
3.1 seg faults
--
nosy: +brian.curtin
stage: ->
Brian Curtin added the comment:
You could use the test skipping functionality present in trunk and beyond.
Write a function to test whether the user has the necessary privileges, then
use @unittest.skipUnless(has_admin_privs(), "can't test as re
Brian Curtin added the comment:
http://www.python.org/psf/contrib/ has the relevant contributor agreement.
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue7
Changes by Brian Curtin :
--
components: +Library (Lib) -None
priority: -> normal
stage: -> test needed
type: -> behavior
versions: -Python 2.5
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
--
keywords: +needs review
nosy: +brian.curtin
priority: -> low
stage: -> patch review
type: -> feature request
versions: +Python 2.7
___
Python tracker
<http://bugs.python.o
Brian Curtin added the comment:
Passes on Windows, Mac, and Linux.
--
___
Python tracker
<http://bugs.python.org/issue3426>
___
___
Python-bugs-list mailin
Brian Curtin added the comment:
Seems like a good idea to me, but maybe not as the default?
--
keywords: +needs review
nosy: +brian.curtin
priority: -> normal
___
Python tracker
<http://bugs.python.org/iss
Changes by Brian Curtin :
--
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
versions: +Python 2.7, Python 3.2 -Python 2.5
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> test needed
___
Python tracker
<http://bugs.python.org/issue7741>
___
__
Changes by Brian Curtin :
--
keywords: +needs review
nosy: +brian.curtin
priority: -> normal
stage: -> patch review
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
components: +None
keywords: +needs review
priority: -> normal
stage: -> patch review
type: -> behavior
versions: +Python 2.7
___
Python tracker
<http://bugs.python.o
Brian Curtin added the comment:
This was handled in r65241 as a result of #1819.
--
nosy: +brian.curtin
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
superseder: -> Speed hack for function calls with name
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> test needed
type: -> behavior
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
Removed file: http://bugs.python.org/file15265/issue4722_20091104_v1.patch
___
Python tracker
<http://bugs.python.org/issue4722>
___
___
Pytho
Brian Curtin added the comment:
On Windows 7, I see the issue as both a regular user and one with admin
privileges. The patch (updated to fix tab/space difference) seems to do the
trick.
Gabriel, which OS are you on that this works differently based on the user
privileges?
I'm stil
Changes by Brian Curtin :
--
resolution: -> rejected
___
Python tracker
<http://bugs.python.org/issue7745>
___
___
Python-bugs-list mailing list
Unsubscri
Brian Curtin added the comment:
I'm not seeing this on 2.5, 2.6, or trunk.
--
components: +Extension Modules
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
title: pydoc error -> pydoc error - "No module named tempfile"
__
Changes by Brian Curtin :
--
keywords: +needs review
___
Python tracker
<http://bugs.python.org/issue2202>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Curtin added the comment:
You can see the same thing by doing execfile(".\test.py"), which is what pdb
makes under the hood, then bdb exec's it.
--
nosy: +brian.curtin
priority: -> normal
stage: -> test needed
type: -> behavior
__
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> test needed
type: crash -> behavior
___
Python tracker
<http://bugs.python.o
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> normal
stage: -> test needed
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/
Changes by Brian Curtin :
--
keywords: +needs review
priority: -> high
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue7753>
___
___
Brian Curtin added the comment:
Works for me, repr will escape the slash.
--
___
Python tracker
<http://bugs.python.org/issue7750>
___
___
Python-bugs-list mailin
Brian Curtin added the comment:
Can you add your test to Lib/test/test_pdb.py?
If the test fails the "hello world" script won't be removed, it won't make it
to os.remove(). You'll need to make sure the file gets deleted in any case.
Could use a temporary file.
Can y
Changes by Brian Curtin :
--
nosy: +brian.curtin
___
Python tracker
<http://bugs.python.org/issue7753>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Brian Curtin :
--
keywords: +needs review
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue7076>
___
___
Python-bugs-list mai
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:
New submission from Brian Harring :
Under py3.1, translation of the attached file works fine- under py3.2, goes
boom however.
Nothing custom in use here in terms of 2to3- there is some compatibility code
in use w/in the module but that's not affecting the translator in my testing.
asse
New submission from Brian Harring :
Bit like unittest, right now it's rather hard to extend 2to3 for caching
support (and other outputs) w/out duplicating the main function.
Attached is a patch that allows the refactoring tool class to be passed in- at
the very least, this patch is enou
Brian Harring added the comment:
Attached is a derivative of
http://pkgcore.org/trac/pkgcore/browser/ferringb/snakeoil-dev/snakeoil/caching_2to3.py
As you can see in that function, some nastyness is required right now to slip
it in w/out duplicating code (hence the first patch).
Patch
Changes by Brian Harring :
--
nosy: +ferringb
___
Python tracker
<http://bugs.python.org/issue1943>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Harring added the comment:
@martin:
Yeah... that's probably the better approach, although seperation of processes
(in terms of setup.py triggering conversion) has some benefits.
The reason I used process seperation and invocation of main was to protect my
distutils extensions ag
Changes by Brian Curtin :
--
components: -2to3 (2.x to 3.0 conversion tool)
stage: -> patch review
type: -> behavior
___
Python tracker
<http://bugs.python.org/
601 - 700 of 1992 matches
Mail list logo
