Antoine Pitrou [EMAIL PROTECTED] added the comment:
If you remove the print() call from joining_func(), does it stop
hanging? It may be due to differences between the io library in py3k and
the builtin file objects in 2.x.
(looking at the date of the commit disabling the test, it is not related
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Let's retarget it to 3.1 then. It's a new feature, not a behaviour
change or a deprecation, so adding it to 3.0 isn't a necessity.
--
components: +Library (Lib)
nosy: +pitrou
priority: release blocker - critical
versions: +Python 3.1
Maciek Fijalkowski [EMAIL PROTECTED] added the comment:
Next wave of tests - error handling. More specifically all errors that
might happen during parsing XML and reported by parser itself.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2982
New submission from Mark Dickinson [EMAIL PROTECTED]:
On a 64-bit OS X build of Python, built with:
./configure --with-universal-archs=64-bit --enable-universalsdk=/
MACOSX_DEPLOYMENT_TARGET=10.5
make
I get the following result:
Python 2.6b2+ (trunk:65805M, Aug 18 2008, 10:59:08)
[GCC
Changes by Antoine Pitrou [EMAIL PROTECTED]:
--
nosy: +pitrou
priority: - normal
versions: +Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2982
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Are many people using OpenDNS? Is there a way to detect that OpenDNS is
being used and trigger a separate path in the test?
I say that because returning a 404 when the domain lookup has failed is
wrong. Perhaps the test should check for a 404
Mark Dickinson [EMAIL PROTECTED] added the comment:
It turns out that uid_t (and gid_t) actually *is* an unsigned 32-bit
integer type on OS X 10.5, so perhaps the pw_uid and pw_gid values are
correct. So to rephrase: one or both of the following facts might be
considered bugs:
(1) On a
Andrew Dalke [EMAIL PROTECTED] added the comment:
Yes, that installed Python 2.6 into the correct location (C:\Python26
instead of into the root directory).
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2271
New submission from Misha Seltzer [EMAIL PROTECTED]:
import re
regex = r[\w]+
# Normal behaviour:
re.findall(regex, hello world, re.M)
['hello', 'world']
re.compile(regex).findall(hello world)
['hello', 'world']
# Bug behaviour:
re.compile(regex).findall(hello world, re.M)
['rld']
New submission from Konrad Hinsen [EMAIL PROTECTED]:
On a MacOS X framework build, the LINKFORSHARED variable obtained from
distutils.sysconfig.get_config_vars() has the value
-u _PyMac_Error Python.framework/Versions/2.5/Python
The last item is incomplete, it needs to be prefixed with the
Nick Coghlan [EMAIL PROTECTED] added the comment:
numbers.Number change forward ported to Py3k in r65808
Docs updated for 2.6 and 3.0 in r65810 and r65811 respectively.
Which means I can finally close this one :)
--
resolution: - fixed
status: open - closed
Antoine Pitrou [EMAIL PROTECTED] added the comment:
The re.M flag is an attribute of the compiled pattern, and as such it
must be passed to compile(), not to findall().
These all work:
re.compile(r[a-z]+).findall(hello world)
['hello', 'world']
re.compile(r[a-z]+, re.M).findall(hello world)
New submission from Nick Coghlan [EMAIL PROTECTED]:
The package level imports from the new multiprocessing package exhibit
some very strange behaviour because they are actually functions
pretending to be classes:
Python 2.6b1+ (trunk:64945, Jul 14 2008, 20:00:46)
[GCC 4.1.3 20070929
Nick Coghlan [EMAIL PROTECTED] added the comment:
Setting to deferred blocker, since this really needs to be dealt with
for RC1 (probably too close to b3 to get it discussed and dealt with for
that).
--
priority: critical - deferred blocker
___
Nick Coghlan [EMAIL PROTECTED] added the comment:
I created issue 3589 to cover the problem I mentioned above with the
very misleading names for the package level functions in multiprocessing.
___
Python tracker [EMAIL PROTECTED]
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
I do not reproduce the problem, but in your example, the trace function
is called only when the script has finished, i.e during interpreter
shutdown. Creating a thread from there is not recommended...
Can you provide the complete
Changes by Amaury Forgeot d'Arc [EMAIL PROTECTED]:
--
assignee: - amaury.forgeotdarc
nosy: +amaury.forgeotdarc
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3496
___
Raghuram Devarakonda [EMAIL PROTECTED] added the comment:
The other failure is trivial, I've fixed it in r65780.
#1709112 has been reported earlier in relation to pagefile.sys. Your
patch addresses at least part of the problem there. I wonder if that
issue can be closed.
--
nosy:
Antoine Pitrou [EMAIL PROTECTED] added the comment:
According to the aforementioned bug report, we should also add a test
for e.winerror == 5. Chances are that other cases will arise one day or
another...
Since the purpose of the test is, allegedly, to Verify that an open
file can be stat'ed,
Matt Giuca [EMAIL PROTECTED] added the comment:
Hi,
Sorry to bump this, but you (Guido) said you wanted this closed by
Wednesday. Is this patch committable yet? (There are no more unresolved
issues that I am aware of).
___
Python tracker [EMAIL PROTECTED]
Antoine Pitrou [EMAIL PROTECTED] added the comment:
The delayed import functions in multiprocessing.__init__ look like a
serious misfeature to me. I'd be inclined to replace them with from
.synchronize import * and from .process import *
+1
(or, even better, qualified than wildcard imports)
Raghuram Devarakonda [EMAIL PROTECTED] added the comment:
On Mon, Aug 18, 2008 at 10:28 AM, Antoine Pitrou [EMAIL PROTECTED] wrote:
Since the purpose of the test is, allegedly, to Verify that an open
file can be stat'ed, it may be simpler to create and open a file
ourselves
Jean-Michel Fauth [EMAIL PROTECTED] added the comment:
Py3.0b2. This bug seems to be quite annoying. Especially when one works
with a main module importing modules which are importing modules and so
on, all modules having an encoding declaration. The Traceback (and the
user) is (are) a little
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Amaury, if you are going to look at this you might want to see #2234.
--
nosy: +benjamin.peterson
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3496
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Actually, this may be a requirement of #2394; PEP 3118 states that
memoryview.tolist would use the struct module to do the unpacking.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3132
New submission from Edward K Ream [EMAIL PROTECTED]:
While porting Leo to Python 3.0, I found that passing any byte stream to
xml.sax.parser.parse will hang the parser. My quick fix was to change:
while buffer != :
to:
while buffer != and buffer != b:
at line 123 of xmlreader.py
Benjamin Peterson [EMAIL PROTECTED] added the comment:
It should probably be changed to just while buffer != b since it
requests a byte stream.
--
nosy: +benjamin.peterson
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3590
Edward K Ream [EMAIL PROTECTED] added the comment:
On Mon, Aug 18, 2008 at 10:09 AM, Benjamin Peterson
[EMAIL PROTECTED]wrote:
Benjamin Peterson [EMAIL PROTECTED] added the comment:
It should probably be changed to just while buffer != b since it
requests a byte stream.
That was my guess
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Actually, this may be a requirement of #2394; PEP 3118 states that
memoryview.tolist would use the struct module to do the unpacking.
:-(
However, we don't have any examples of the buffer API / memoryview
object working with something else
Benjamin Peterson [EMAIL PROTECTED] added the comment:
I've been trying to do this for a little, but I can't actually figure
out how to implement the warnings. If anyone has any advice on this I'd
be very thankful! Anyway, you're right in that this doesn't need to
block betas.
--
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Mmmh, the problem with the list(X.items()) idiom is that it's
thread-safe only if X.items() is implemented in C. Otherwise X can be
mutated if there is a thread-switch while executing bytecode in X.items().
In weakref.py (line 103), by
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
I managed to get a proper traceback:
Exception in Tkinter callback
Traceback (most recent call last):
File c:\afa\python\py3k\lib\tkinter\__init__.py, line 1405, in __call__
return self.func(*args)
File
Robert Schuppenies [EMAIL PROTECTED] added the comment:
You are right. How about the attached patch, do you see any problems
here? Tkinter seems to ignore any delete calls when either of the
indices is None, so the deletion of commands may be ignored as well. But
I couldn't find a description
Benjamin Peterson [EMAIL PROTECTED] added the comment:
I think I can get this done before the release now. For starters I
changed thread.get_ident() to a property in r65818.
--
assignee: - benjamin.peterson
___
Python tracker [EMAIL PROTECTED]
New submission from Antoine Pitrou [EMAIL PROTECTED]:
In py3k, there should be explicit tests for byte string input (in
addition to unicode input) to elementtree's parser, including non-UTF8
encodings and non-ASCII chars.
--
components: Tests, XML
messages: 71351
nosy: effbot, pitrou
Brett Cannon [EMAIL PROTECTED] added the comment:
On Mon, Aug 18, 2008 at 3:52 AM, Antoine Pitrou [EMAIL PROTECTED] wrote:
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Are many people using OpenDNS? Is there a way to detect that OpenDNS is
being used and trigger a separate path in
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Le lundi 18 août 2008 à 17:19 +, Brett Cannon a écrit :
That's also a possibility.
Out of curiosity, what HTTP response should be received?
There shouldn't be an HTTP response at all. If DNS lookup fails,
connecting to the server
Nick Edds [EMAIL PROTECTED] added the comment:
What's the current status of this? If nobody is working on it, I would
be willing to give it a shot. Can somebody just confirm that I have a
correct understanding of the problem.
UserDict.UserDict needs a deprecation warning,
Brett Cannon [EMAIL PROTECTED] added the comment:
On Mon, Aug 18, 2008 at 10:59 AM, Nick Edds [EMAIL PROTECTED] wrote:
Nick Edds [EMAIL PROTECTED] added the comment:
What's the current status of this?
I think it is waiting for someone to work on it.
If nobody is working on it, I would
be
Guido van Rossum [EMAIL PROTECTED] added the comment:
Looking into this now. Will make sure it's included in beta3.
--
assignee: - gvanrossum
priority: - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3300
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Ok. I've done the threading API and patched up multiprocessing so it
actually works. Jesse, can you do multiprocessing?
Also, can we decide about is_alive as a property?
--
assignee: benjamin.peterson - jnoller
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Oh, and by the way, I would start working on multiprocessing by
reverting r65828.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3352
___
Jesse Noller [EMAIL PROTECTED] added the comment:
On Mon, Aug 18, 2008 at 2:44 PM, Benjamin Peterson
[EMAIL PROTECTED] wrote:
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Ok. I've done the threading API and patched up multiprocessing so it
actually works. Jesse, can you do
Jesse Noller [EMAIL PROTECTED] added the comment:
On Mon, Aug 18, 2008 at 2:45 PM, Benjamin Peterson
[EMAIL PROTECTED] wrote:
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Oh, and by the way, I would start working on multiprocessing by
reverting r65828.
Makes sense.
Antoine Pitrou [EMAIL PROTECTED] added the comment:
From the discussion on the python-3000, it looks like it would be nice
if sax.parser handled both bytes and unicode streams.
Edward, does your simple fix make sax.parser work entirely well with
byte streams?
Fabio Zadrozny [EMAIL PROTECTED] added the comment:
I've pasted the output below... also, the trace function is called for
each function call after the settrace (not only in interpreter shutdown)
-- and the error happens in the listdir -- which is in the main thread,
so, it must happen before
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Yes, this problem is a duplicate of #2234, for which I had a very
similar fix.
Thanks!
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Fixed by r65834, thanks to the patch provided in issue3496.
Will backport.
--
nosy: +amaury.forgeotdarc
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
committed r65835 in the release25-maint branch.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2234
___
Ismail Donmez [EMAIL PROTECTED] added the comment:
py3k branch gives another error now, when running test_multiprocessing
in a tight loop:
test test_multiprocessing failed -- Traceback (most recent call last):
File /Users/cartman/Sources/py3k/Lib/test/test_multiprocessing.py,
line 1163, in
Jesse Noller [EMAIL PROTECTED] added the comment:
Ismail, that's the incref bug in issue 3419
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3578
___
___
Ismail Donmez [EMAIL PROTECTED] added the comment:
Ah cool, we might be at the end of multiprocessing problems then I guess
:-)
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3578
___
Jesse Noller [EMAIL PROTECTED] added the comment:
the socket.error: [Errno 111] Connection refused is fixed/resolved with
the fix for issue 3270
--
resolution: - duplicate
status: open - closed
___
Python tracker [EMAIL PROTECTED]
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Le lundi 18 août 2008 à 19:42 +, Ismail Donmez a écrit :
Ismail Donmez [EMAIL PROTECTED] added the comment:
Ah cool, we might be at the end of multiprocessing problems then I guess
:-)
Well, not really, it should be diagnosed why the
Guilherme Polo [EMAIL PROTECTED] added the comment:
change this:
You could return if in that new if statement.
to:
You could return in that new if statement., please.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1342811
Edward K Ream [EMAIL PROTECTED] added the comment:
On Mon, Aug 18, 2008 at 1:51 PM, Antoine Pitrou [EMAIL PROTECTED]wrote:
Antoine Pitrou [EMAIL PROTECTED] added the comment:
From the discussion on the python-3000, it looks like it would be nice
if sax.parser handled both bytes and unicode
Edward K Ream [EMAIL PROTECTED] added the comment:
On Mon, Aug 18, 2008 at 11:00 AM, Antoine Pitrou [EMAIL PROTECTED]wrote:
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Just to be clear, I am at present totally confused about io streams :-)
Python 3.0 distincts more clearly
Fredrik Johansson [EMAIL PROTECTED] added the comment:
Wow, newbie error. Thanks for spotting!
In every case I can think of, I've wanted (0).numbits() to be 0. The
explanation in the docstring can probably be improved. What other
documentation is needed (where)?
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
I could reproduce the problem, and it appears that it is the same as
#1608818, corrected by r65037:
on posix platforms, listdir() used to check for errno only at the end of
the list; the problem is that the trace function creates a
Nick Edds [EMAIL PROTECTED] added the comment:
Ahh right. I totally forgot that there was already a fix_dict.py that
took care of that.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2876
___
New submission from Brett Cannon [EMAIL PROTECTED]:
Attached is a patch to add imp.get_codingspec(); a function that returns
the encoding of a source file.
The motivation is to remove the import of the re module in linecache to
speed up interpreter startup.
--
components: Library (Lib)
Brett Cannon [EMAIL PROTECTED] added the comment:
It should be noted the original patch by Christian had a check for bad
tokenizing. Turns out that if you have that in several tests fail,
including test_modulefinder. This might mean there is a deeper problem
in the parser.
Antoine Pitrou [EMAIL PROTECTED] added the comment:
The same calls to sax read the file correctly on Python 2.5.
What are those calls exactly?
Why is cp1252 used as an encoding? Is it what is specified in the XML
file? Or do you somehow feed stdin to the SAX parser? (if the latter,
you aren't
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
I guess that the file is simply opened in text mode (r). This uses the
preferred encoding, which is cp1252 on (western) Windows machines.
--
nosy: +amaury.forgeotdarc
___
Python tracker [EMAIL
Fabio Zadrozny [EMAIL PROTECTED] added the comment:
Thanks for looking into this...
Unfortunately, I'm not sure I can use the workaround of the int('0'), as
this could fix the debugger, but if the code that's being debugged
spawned other threads (which is pretty common), it would be pointless,
Mark Dickinson [EMAIL PROTECTED] added the comment:
In every case I can think of, I've wanted (0).numbits() to be 0.
Me too, in most cases, though I've encountered the occasional case where
raising ValueError would be more appropriate and would catch some bugs
that might otherwise pass
New submission from Miki Tebeka [EMAIL PROTECTED]:
The attached script hangs on Ubuntu + Python 2.5.2.
When make the limit smaller (like 10) or not redirecting stdout, it works.
Running the svn command from shell took about 4sec, I gave up on the
script after a minute.
I tried it both with svn
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
but if the code that's being debugged
spawned other threads (which is pretty common), it would be pointless,
No, the problem specifically lies in the implementation of listdir().
This function is not supposed to commonly spawn
Guido van Rossum [EMAIL PROTECTED] added the comment:
Checked in patch 10 with minor style changes as r65838.
Thanks Matt for persevering! Thanks everyone else for contributing;
this has been quite educational.
--
resolution: - accepted
status: open - closed
Kevin Watters [EMAIL PROTECTED] added the comment:
I know this is long closed, but no one on the nosy list happens to have
this fix backported to 2.5, do they? :) If not, I'll attach one here
eventually...
--
nosy: +kevinwatters
___
Python tracker
Edward K Ream [EMAIL PROTECTED] added the comment:
On Mon, Aug 18, 2008 at 4:15 PM, Antoine Pitrou [EMAIL PROTECTED]wrote:
Antoine Pitrou [EMAIL PROTECTED] added the comment:
The same calls to sax read the file correctly on Python 2.5.
What are those calls exactly?
parser =
Changes by Antoine Pitrou [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file11145/unnamed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3590
___
___
Changes by Antoine Pitrou [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file11147/unnamed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3590
___
___
Changes by Antoine Pitrou [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file11148/unnamed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3590
___
___
Changes by Antoine Pitrou [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file11151/unnamed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3590
___
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Ok, then xml.sax looks rather broken.
(by the way, can you avoid sending HTML emails? each time you send one,
the bug tracker attaches a file names unnamed. I've removed all 4 of
them now.)
___
Python
Alexandre Vassalotti [EMAIL PROTECTED] added the comment:
Sorry, I can't. I would love to get this done, but I am just too busy
this week (and next week doesn't look any better). Furthermore, the
amount of work that the profile/cProfile merge will require is quite
considerable. So, I don't
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Let's retarget 3.1 then.
--
nosy: +benjamin.peterson
priority: release blocker - critical
versions: +Python 3.1 -Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2919
Terry J. Reedy [EMAIL PROTECTED] added the comment:
I am reopening because my suggested fix was wrong. As pointed out by
Fredrik Lundh on PyDev the next day, quoting from the grammar,
attributes, subscriptions, slicing, and call have the *same* precedence.
I thought I posted his comment and an
Clinton Roy [EMAIL PROTECTED] added the comment:
Thanks for the comments Amaury, this patch uses ${VERSION} throughout so
that it can be applied across branches.
cheers,
Added file: http://bugs.python.org/file11152/pkgconfig.diff
___
Python tracker [EMAIL
New submission from Brett Cannon [EMAIL PROTECTED]:
Turns out that PyTokenizer_FindEncoding() never properly succeeds
because the tok_state used by it does not have tok-filename set, which
is an error condition in the tokenizer. This error has been masked by
the one place the function is used,
Brett Cannon [EMAIL PROTECTED] added the comment:
I have not bothered to check if this exists in 2.6, but I don't see why
it would be any different.
--
type: - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3594
Brett Cannon [EMAIL PROTECTED] added the comment:
Turns out that the NULL return value can signal an error that manifests
itself as SyntaxError(encoding problem: with BOM) thanks to the lack
of tok-filename being set in Parser/tokenizer.c:fp_setreadl() which is
called by check_coding_spec() and
New submission from Ahir Reddy [EMAIL PROTECTED]:
I'm new to this and not quite sure how to go about posting an issue, but
I will do the best I can. In Python 2.5.2, both from python.org and
active state, all methods of decoding in base64 under Windows produce
different output than base64
Brett Cannon [EMAIL PROTECTED] added the comment:
Can someone double-check this patch for me? I don't have much experience
with the parser so I want to make sure I am not doing anything wrong.
___
Python tracker [EMAIL PROTECTED]
Brett Cannon [EMAIL PROTECTED] added the comment:
There is a potential dependency on issue3594 as it would change how
imp.find_module() acts and thus make test_imp no longer fail in the way
it has.
--
dependencies: +PyTokenizer_FindEncoding() never succeeds
Benjamin Peterson [EMAIL PROTECTED] added the comment:
That line dates back to the PEP 263 implementation. Martin?
--
nosy: +benjamin.peterson, loewis
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3574
New submission from Heikki Toivonen [EMAIL PROTECTED]:
There should be a way to disable SSLv2 since it is insecure. It would be
even better if SSLv2 was disabled out of the box, but maybe there could
be a way to re-enable it.
I made the default to disable SSLv2 in M2Crypto, but those that want
Heikki Toivonen [EMAIL PROTECTED] added the comment:
I would definitely recommend providing as strict as possible hostname
verification in the stdlib, but provide application developers a way to
override that.
M2Crypto (and TLS Lite, from which I copied the approach to M2Crypto),
provide a
New submission from Heikki Toivonen [EMAIL PROTECTED]:
The 2.6 documentation states selecting the most compatible SSLv23 mode
may mean low quality ciphers, which does not really help the application
developers. It would be better to provide a way to set the allowed
ciphers. Even better, IMO,
Brett Cannon [EMAIL PROTECTED] added the comment:
Attached is a patch that fixes where the error occurs. By opening the
file by either file name or file descriptor, the problem goes away. Once
this patch is accepted then PyErr_Occurred() should be added to all uses
of PyTokenizer_FindEncoding().
91 matches
Mail list logo
