Gregory P. Smith g...@krypto.org added the comment:
Using issue7242-gps01.diff on release26-maint and a freshly downloaded
opensolaris 2009-06 VM test_thread, test_threading and test_subprocess all pass
for me both before -and- after the patch. Nor does the original thread_test.py
cause the
Lars Gustäbel l...@gustaebel.de added the comment:
Another version of the patch (issue7232.6.diff) that checks if the TarFile
object is still open in the __enter__() method (plus a test for that). I
removed the docstrings as Eric suggested. This is common practice in the
standard library.
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8029
___
___
Greg Jednaszewski jednaszew...@gmail.com added the comment:
The problem only seems to appear on Solaris 9 and earlier. I'll try to test
the updated patch tonight or tomorrow and let you know what I find.
--
___
Python tracker rep...@bugs.python.org
R. David Murray rdmur...@bitdance.com added the comment:
Because the shell argument provides important functionality. Or are you
suggesting that passing a list implies shell=False and passing a string implies
shell=True? That is a possibility, but I think it would not be a good idea,
Eric Smith e...@trueblade.com added the comment:
I think the better design is to have 2 distinct APIs: Popen_shell and
Popen_exec. I'm not wild about the name Popen_exec, suggestions welcome.
Neither of these would accept a shell parameter.
For starters these could be convenience APIs that
Brian Curtin cur...@acm.org added the comment:
That seems reasonable. We already have subprocess.call, the thin wrapper around
Popen. Maybe add this as subprocess.call_shell and call_exec?
--
nosy: +brian.curtin
___
Python tracker
R. David Murray rdmur...@bitdance.com added the comment:
Hmm. I liked Eric's idea, and it would be easier to get in, but 'call' is
actually an argument against it. It would mean that in addition to PopenExec
and PopenShell we'd need call_exec and call_shell, and check_call_exec and
Meador Inge mead...@gmail.com added the comment:
This is common practice in the standard library.
This doesn't necessarily mean it is a correct practice :-). All
kidding aside, I think the assumption that the standard documentation
on '__enter__' and '__exit__' is sufficient is a bad one.
Gregory P. Smith g...@krypto.org added the comment:
If you have a chance tonight that'd be awesome. I'd love to get this in before
2.6.5rc1 (being cut tomorrow) but as its platform specific (and a pretty-old
platform at that) its not worth holding up the release.
--
New submission from Christopher the Magnificent
ultimate.mac.fana...@gmail.com:
Help for list looks like this:
help(list)
class list(object)
| list() - new list
| list(sequence) - new list initialized from sequence's items
|
Help for dict looks like this:
Gregory P. Smith g...@krypto.org added the comment:
fixed in trunk r78517 and release26-maint r78518.
still needs merging into py3k and release31-maint
--
resolution: - accepted
___
Python tracker rep...@bugs.python.org
Lars Gustäbel l...@gustaebel.de added the comment:
IMO it is okay for __enter__() and __exit__() not to have docstrings.
I cannot see what's so special about the behaviour of __enter__() and
__exit__().
__enter__() raises IOError only if the TarFile object has been already closed.
This is
Gregory P. Smith g...@krypto.org added the comment:
r78519 r78520 for py3k and 3.1.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7481
___
Hong Chen cn.hongc...@gmail.com added the comment:
Sorry for the delay, it's been a busy month.
I just tried python 3.1 If installed under c:\program files, the
access control list would be correct, only system administrator
accounts get the modify privilege.
The default installation is to
Gregory P. Smith g...@krypto.org added the comment:
Reviewers: gregory.p.smith, Benjamin, ilya.sandler,
Message:
Also, can you take a look at how the pdb unittests work and see if you
can come up with a way to unittest the KeyboardInterrupt behavior?
Particular for the 4 scenarios you outlined
Gregory P. Smith g...@krypto.org added the comment:
fwiw - The documentation was updated in trunk, py3k and release31-maint to
mention this behavior of assertSameElements.
Assigning to Michael for a decision on whether or not to add to the API.
python-unittest-backport has since been
New submission from Peter Jones pjon...@hughes.net:
I am user 11943. OS is Windows Vista Ultimate. I have followed the instructions
on how to use f2py and get this error when I try it (is this a known bug? It
appears that there is bug in f2py):
C:\Python26\Scriptspython f2py.py
Traceback
New submission from Dave Malcolm dmalc...@redhat.com:
gdb 7 can be extended with Python code, allowing the writing of domain-specific
pretty-printers and commands.
I've been working on gdb 7 hooks to make it easier to debug python itself, as
mentioned here:
Changes by Dave Malcolm dmalc...@redhat.com:
--
keywords: +patch
Added file:
http://bugs.python.org/file16403/add-gdb7-python-hooks-to-trunk.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8032
Benjamin Peterson benja...@python.org added the comment:
This is a 3rd party package problem. Please ask the maintainers of it.
--
nosy: +benjamin.peterson
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
Peter Jones pjon...@hughes.net added the comment:
I would like to recall this bug report. What happend was I went to the f2py
web site and dowloaded the latest version and installed it over Pythoh
x,y. So I uninstalled P x,y and resinstalled and the f2py works OK now. Some
one should make it
Greg Jednaszewski jednaszew...@gmail.com added the comment:
I tested the updated patch, and the new unit test passes on my Sol 8 sparc, but
the test_threading test still hangs on my system. However, given that the test
is skipped on several platforms and it does work on more relevant versions
David Watson bai...@users.sourceforge.net added the comment:
Thanks for your interest! I'm actually still working on the
patch I posted, docs and a test suite, and I'll post something
soon.
Yes, you could just use b.join() with sendmsg() (and get
slightly annoyed because it doesn't accept
Gregory P. Smith g...@krypto.org added the comment:
r.david.murray - sounds like a good idea.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3892
___
New submission from Fred Fettinger fetti...@gmail.com:
Handling of long integers is broken for arguments to sqlite functions created
with the create_function api. Integers passed to a sqlite function are always
converted to int instead of long, which produces an incorrect value for
integers
Fred Fettinger fetti...@gmail.com added the comment:
I've never really looked at the python source before, but this is my best guess
at the problem:
For the standard SELECT query:
In Modules/_sqlite/cursor.c, _pysqlite_fetch_one_row() has this code:
PY_LONG_LONG intval;
...
} else if (coltype
Ryan Coyner rcoy...@gmail.com added the comment:
You don't want to do c_size_t = c_void_p because that will prevent type
checking. We want c_size_t to be integers; setting it to c_void_p will accept
other values. The lines that define c_size_t are doing a sizeof check to
determine how many
Éric Araujo mer...@netwok.org added the comment:
Hello
This is indeed a problem with f2py. Please tell its maintaines that they can’t
name an object “as” since it’s a reserved keyword in Python 2.6 and higher.
Testing with 2.5 (previous stable version, released in 2006) would have shown
it:
Éric Araujo mer...@netwok.org added the comment:
While I’m thinking about this, is there a way to make the syntax error
traceback more informative, i.e. adding “'{}' is a reserved keyword” in such
cases?
--
___
Python tracker rep...@bugs.python.org
Antoine Pitrou pit...@free.fr added the comment:
lazy sounds like a bad name for that parameter. It makes me think of lazy
evaluation, not error checking.
There's also the problem that check_py3k_warnings() will check all
DeprecationWarnings, not only py3k-specific ones. We need a
Changes by Gregory P. Smith g...@krypto.org:
--
nosy: +gregory.p.smith
priority: - normal
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8032
___
Gregory P. Smith g...@krypto.org added the comment:
In PC/pyconfig.h we #define Py_WINVER to _WIN32_WINNT_WIN2K (0x500) for 32bit
builds.
I think we should update this to _WIN32_WINNT_WINXP (0x501) for all builds,
not just 64bit.
Assigning to loewis as he does our windows release builds
Martin v. Löwis mar...@v.loewis.de added the comment:
Bumping the API level to XP might mean that we stop supporting Windows 2000;
I'm not sure whether we agreed to that yet.
I'd be curious to find out why the constants were defined in Python 2.5.
--
Gregory P. Smith g...@krypto.org added the comment:
extended support for windows 2000 server ends in a few months, mainstream
support ended 5 years ago:
http://support.microsoft.com/lifecycle/?LN=en-usx=8y=9p1=7274
That, IMNSHO, implies that python 2.7 and 3.2 should not bother supporting
35 matches
Mail list logo
