[issue9545] Adding _collections to static build

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Re msg113792: Nick, running the clean step before configure is not possible. It 
requires a Makefile, which isn't there yet.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue444582] Finding programs in PATH, adding shutil.which

[Iztok Kavkler]

Iztok Kavkler  added the comment:

There is a subtle problem in the reference implementation: it will break if one 
of the paths in PATH contains quoted path separator. On windows that would be 
quted with ":

"c:\path;with;sep"

and on *nix something like

/path\:with\:sep

The problem is in the call
path.split(os.path.sep)
To do this properly we would need another helper function, e.g. 
shutil.split_path_list(path)
that would split paths considering quoting. I should also strip quotes  from 
every path in the list. 

I would write reference implementation, but I'm not sure if I know all the 
quoting rules of various os-es.

--
nosy: +Iztok.Kavkler

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9603] os.ttyname() and os.ctermid() don't decode result according to PEP 383

[STINNER Victor]

STINNER Victor  added the comment:

Commited to 3.1 as r84061 and to 3.2 as r84060. Thanks David.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9545] Adding _collections to static build

[Nick Coghlan]

Nick Coghlan  added the comment:

On Sun, Aug 15, 2010 at 6:44 PM, Martin v. Löwis  wrote:
>
> Martin v. Löwis  added the comment:
>
> Re msg113792: Nick, running the clean step before configure is not possible. 
> It requires a Makefile, which isn't there yet.

Ah, of course. Still, the fix to run the clean step even if the
compile fails should at least help the issue.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9604] os.initgroups() doesn't accept PEP 383 usernames returned by pwd module

[STINNER Victor]

STINNER Victor  added the comment:

Commited to 3.2 as r84062. Thanks David.

(Python 3.1 has no posix.initgroups() function)

--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9605] os.getlogin() should use PEP 383 decoding to match the pwd module

[STINNER Victor]

STINNER Victor  added the comment:

Commited to 3.1 as r84064 and to 3.2 as r84063. Thanks David.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9608] Re-phrase best way of using exceptions in doanddont.rst

[Floris Bruynooghe]

New submission from Floris Bruynooghe :

The description of how to best use exceptions is slightly confusing and led me 
to believe there was an issue when using open() as a context manager.  The main 
issue is that the wording seems to suggest the example above it is the best and 
not the very last.

Attached is a patch which uses a slightly different wording which IMHO makes it 
clearer that the with-statement is the preferred method and does not introduce 
subtle bugs.

--
assignee: d...@python
components: Documentation
files: doandont.diff
keywords: patch
messages: 113949
nosy: d...@python, flub
priority: normal
severity: normal
status: open
title: Re-phrase best way of using exceptions in doanddont.rst
type: feature request
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3
Added file: http://bugs.python.org/file18538/doandont.diff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9607] Test file 'test_keyword.py' submission for use with keyword.py

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +benjamin.peterson

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1710703] zipfile.ZipFile behavior inconsistent.

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Two nits:
- bug fixes shouldn't have a "versionadded" or "versionchanged" entry (it's 
only for new features)
- Misc/NEWS should be in antichronological order

--
nosy: +pitrou

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9545] Adding _collections to static build

[Eli Bendersky]

Eli Bendersky  added the comment:

Compiling py3k from main repo doesn't work:
ould not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
Traceback (most recent call last):
  File "/home/eliben/python_src/eliben-py3k/Lib/site.py", line 540, in 
main()
  File "/home/eliben/python_src/eliben-py3k/Lib/site.py", line 522, in main
known_paths = addusersitepackages(known_paths)
  File "/home/eliben/python_src/eliben-py3k/Lib/site.py", line 249, in 
addusersitepackages
user_site = getusersitepackages()
  File "/home/eliben/python_src/eliben-py3k/Lib/site.py", line 224, in 
getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
  File "/home/eliben/python_src/eliben-py3k/Lib/site.py", line 214, in 
getuserbase
USER_BASE = get_config_var('userbase')
  File "/home/eliben/python_src/eliben-py3k/Lib/sysconfig.py", line 553, in 
get_config_var
return get_config_vars().get(name)
  File "/home/eliben/python_src/eliben-py3k/Lib/sysconfig.py", line 435, in 
get_config_vars
import re
  File "/home/eliben/python_src/eliben-py3k/Lib/re.py", line 121, in 
import functools
  File "/home/eliben/python_src/eliben-py3k/Lib/functools.py", line 15, in 

from collections import OrderedDict
  File "/home/eliben/python_src/eliben-py3k/Lib/collections.py", line 9, in 

from _collections import deque, defaultdict
ImportError: No module named _collections
[27060 refs]
make: *** [sharedmods] Error 1

--

I re-ran configure, ran 'make clean' then 'make', doesn't help. The error and 
the HG log make me suspect it might be this issue's fix that's involved.

--
nosy: +eli.bendersky

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1710703] zipfile.ZipFile behavior inconsistent.

[Georg Brandl]

Georg Brandl  added the comment:

Agreed with Antoine.  Do you want to commit?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8844] Condition.wait() doesn't raise KeyboardInterrupt

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> Added a patch that adds support for recomputing the timeout, plus a test for 
> it.
> 
> Can this still make it into 3.2, or is it too disruptive at this point
> in the release process?

No problem at this point, we're not yet in beta phase.
I haven't looked at the patch itself, but thank you.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9545] Adding _collections to static build

[Eli Bendersky]

Eli Bendersky  added the comment:

`make distclean` worked for me (tipped at #python-dev), after it ./configure 
and make succeeded. I must say it's not 100% intuitive, I'm used to just using 
`make clean` for a complete cleanup.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9425] Rewrite import machinery to work with unicode paths

[Florent Xicluna]

Florent Xicluna  added the comment:

r83972 breaks OS X buildbots: support.TESTFN_UNENCODABLE is not defined if 
sys.platform == 'darwin'.

  File "/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/test/test_imp.py", line 
309, in 
class NullImporterTests(unittest.TestCase):
  File "/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/test/test_imp.py", line 
310, in NullImporterTests
@unittest.skipIf(support.TESTFN_UNENCODABLE is None,
AttributeError: 'module' object has no attribute 'TESTFN_UNENCODABLE'

--
keywords: +buildbot
nosy: +flox

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9425] Rewrite import machinery to work with unicode paths

[Florent Xicluna]

Florent Xicluna  added the comment:

It breaks test_unicode_file on OS X, too:

  File 
"/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/test/test_unicode_file.py", 
line 8, in 
from test.support import (run_unittest, rmtree,
ImportError: cannot import name TESTFN_UNENCODABLE

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8857] socket.getaddrinfo needs tests

[Florent Xicluna]

Florent Xicluna  added the comment:

test_socket fails on OS X:

==
ERROR: testGetaddrinfo (test.test_socket.GeneralModuleTests)
--
Traceback (most recent call last):
  File "/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/test/test_socket.py", 
line 611, in testGetaddrinfo
socket.getaddrinfo(HOST, None, 0, 0, socket.AI_CANONNAME)
socket.gaierror: [Errno 12] Bad hints

--

http://www.python.org/dev/buildbot/all/builders/x86%20Tiger%203.x/builds/791

--
keywords: +buildbot
nosy: +flox
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8428] buildbot: test_multiprocessing timeout (test_notify_all? test_pool_worker_lifetime?)

[Florent Xicluna]

Florent Xicluna  added the comment:

Seen on Windows 7 3.1:

test test_multiprocessing failed -- Traceback (most recent call last):
  File 
"D:\cygwin\home\db3l\buildarea\3.1.bolen-windows7\build\lib\test\test_multiprocessing.py",
 line 746, in test_notify_all
self.assertReturnsIfImplemented(6, get_value, woken)
  File 
"D:\cygwin\home\db3l\buildarea\3.1.bolen-windows7\build\lib\test\test_multiprocessing.py",
 line 120, in assertReturnsIfImplemented
return self.assertEqual(value, res)
AssertionError: 6 != 2


There's a second issue at the end of the log, it seems to be the case 3 of 
issue #9592 (RuntimeError: maximum recursion depth exceeded while calling a 
Python object).

http://www.python.org/dev/buildbot/all/builders/x86%20Windows7%203.1/builds/676

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9592] Limitations in objects returned by multiprocessing Pool

[Florent Xicluna]

Florent Xicluna  added the comment:

Case 3 seen on buildbot Windows 7 3.1:

http://www.python.org/dev/buildbot/all/builders/x86%20Windows7%203.1/builds/676

test_array (test.test_multiprocessing.WithProcessesTestArray) ... Traceback 
(most recent call last):
  File "", line 1, in 
  File 
"D:\cygwin\home\db3l\buildarea\3.1.bolen-windows7\build\lib\multiprocessing\forking.py",
 line 344, in main
self = load(from_parent)
  File "D:\cygwin\home\db3l\buildarea\3.1.bolen-windows7\build\lib\pickle.py", 
line 1356, in load
encoding=encoding, errors=errors).load()
  File 
"D:\cygwin\home\db3l\buildarea\3.1.bolen-windows7\build\lib\unittest.py", line 
1363, in __getattr__
return getattr(self.stream,attr)
(...)
  File 
"D:\cygwin\home\db3l\buildarea\3.1.bolen-windows7\build\lib\unittest.py", line 
1363, in __getattr__
return getattr(self.stream,attr)
RuntimeError: maximum recursion depth exceeded while calling a Python object

--
keywords: +buildbot
nosy: +flox

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9592] Limitations in objects returned by multiprocessing Pool

[Florent Xicluna]

Florent Xicluna  added the comment:

A different issue on XP-5 buildbot (Python 3.1):

test test_multiprocessing failed -- Traceback (most recent call last):
  File 
"C:\buildslave\3.1.moore-windows\build\lib\test\test_multiprocessing.py", line 
1234, in test_rapid_restart
manager.shutdown()
  File "C:\buildslave\3.1.moore-windows\build\lib\multiprocessing\util.py", 
line 174, in __call__
res = self._callback(*self._args, **self._kwargs)
  File "C:\buildslave\3.1.moore-windows\build\lib\multiprocessing\managers.py", 
line 602, in _finalize_manager
process.terminate()
  File "C:\buildslave\3.1.moore-windows\build\lib\multiprocessing\process.py", 
line 111, in terminate
self._popen.terminate()
  File "C:\buildslave\3.1.moore-windows\build\lib\multiprocessing\forking.py", 
line 276, in terminate
_subprocess.TerminateProcess(int(self._handle), TERMINATE)
WindowsError: [Error 5] Access is denied


Then, on replay, it ended with the "RuntimeError: maximum recursion depth 
exceeded while calling a Python object" like the Windows 7 case.


http://www.python.org/dev/buildbot/all/builders/x86%20XP-5%203.1/builds/581

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9295] test_close_open_print_buffered(test_file) sometimes crashes

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> Is freeing the memory allocated for setvbuf() while close() running in 
> another thread really safe?

I don't know. I guess nobody does that.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9545] Adding _collections to static build

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Considering the notice

---
Modules/Setup.dist is newer than Modules/Setup;
check to make sure you have all the updates you
need in your Modules/Setup file.
Usually, copying Modules/Setup.dist to Modules/Setup will work.
---

also would have solved the problem.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8857] socket.getaddrinfo needs tests

[Florent Xicluna]

Changes by Florent Xicluna :


--
nosy: +ronaldoussoren

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9592] Limitations in objects returned by multiprocessing Pool

[Jesse Noller]

Jesse Noller  added the comment:

Florent - Are you running the script from Freek on the buildbots, or are you 
just updating this bugs with other run failures? I'm having a really hard time 
separating things.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9609] make cProfile multi-stack aware

[Kristján Valur Jónsson]

New submission from Kristján Valur Jónsson :

One of the problems with the profiling modules provided with Python is that 
they are not useful in the presence of multiple threads.  This is because time 
spent in a different thread may be falsely attributed to some random place in a 
thread being profiled.

This patch helps fix that, by making the _lsprof.c module (the engine behind 
cProfile) multi-stack aware.  At every entry into the profiler, a check is made 
to see which stack is in operation (by looking at the thread state).  The 
previous stack is then paused and profiling commences on the new stack.

Time spent on other stacks is then subtracted from the measured time on each 
stack.

A complication arises because it is no longer possible to determine the 
recursion level of each function (or subcall instance) on each stack by looking 
at the function's entry alone.  For this reason, it becomes necessary to walk 
the stack in cases where there are multiple stacks and multiple total 
recursions seen for the entries.

This patch has been successfully used, with a modifiaction for stackless 
python, in production at CCP (the modification uses the Tasklet ID rather than 
the TLS pointer as a key to the stack map).

To be useful, it is important that all threads in the process are set to use 
the same cProfile.Profiler() instance.  Currently there is no easy way to do 
that and this patch doesn't attempt to fix that.  But is is possible that an 
application designed for profiling would attach the profiler at each thread 
start point.  (In the version of Stackless Python that this is used on, it is 
possible to enable tracing/profiling of all tasklets simultaneously)

--
components: Extension Modules
files: _lsprof.patch
keywords: patch, patch
messages: 113964
nosy: krisvale
priority: normal
severity: normal
status: open
title: make cProfile multi-stack aware
type: feature request
versions: Python 3.2
Added file: http://bugs.python.org/file18539/_lsprof.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8428] buildbot: test_multiprocessing timeout (test_notify_all? test_pool_worker_lifetime?)

[Jesse Noller]

Jesse Noller  added the comment:

Is this intermittent, or consistently failing? Updating it with more buildbot 
failures doesn't help.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9592] Limitations in objects returned by multiprocessing Pool

[Florent Xicluna]

Florent Xicluna  added the comment:

It is an update with 2 similar failures on Windows XP and 7 buildbots (on 
normal runs).

FWIW, I ran the script from Freek on my laptop (Debian 64bits) and I noticed 
similar failures on 3.1 and 3.2 (you need to uncomment 1 of the 3 commented 
lines of the script to see the failures).

--
versions: +Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8428] buildbot: test_multiprocessing timeout (test_notify_all? test_pool_worker_lifetime?)

[Florent Xicluna]

Florent Xicluna  added the comment:

It is intermittent on most buildbots.
The exception is "x86 FreeBSD 7.2 3.x" where it occurs on each run.

http://www.python.org/dev/buildbot/all/builders/x86%20FreeBSD%207.2%203.x/

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8739] Update to smtpd.py to RFC 5321

[Giampaolo Rodola']

Giampaolo Rodola'  added the comment:

Patch no longer applies cleanly because smtpd.py changed in the meantime. A 
further comment:

-def __init__(self, server, conn, addr):
+def __init__(self, server, conn, addr, size = 0):
-def __init__(self, localaddr, remoteaddr):
+def __init__(self, localaddr, remoteaddr, size = 0):

This change breaks backward compatibility. I think it would be better to 
provide this as a SMTPChannel.size_limit class attribute.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

[Jesse Noller]

Jesse Noller  added the comment:

looks fine mark

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8857] socket.getaddrinfo needs tests

[Giampaolo Rodola']

Giampaolo Rodola'  added the comment:

Is there someone who can take a look at this on OSX (Ronald?)?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8845] Expose sqlite3 connection inTransaction as read-only in_transaction attribute

[Florent Xicluna]

Changes by Florent Xicluna :


--
components: +Macintosh
keywords: +buildbot

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8845] Expose sqlite3 connection inTransaction as read-only in_transaction attribute

[Florent Xicluna]

Changes by Florent Xicluna :


--
nosy: +flox

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9610] buildbot: uncaptured python exception (smtpd), but no failure in regrtest

[Florent Xicluna]

New submission from Florent Xicluna :

It occurs on PPC Leopard 3.x buildbot.

(...)
[184/346] test_ssl
error: uncaptured python exception,
closing channel 
(:pop from empty list
[/Users/buildbot/buildarea/3.x.parc-leopard-1/build/Lib/asyncore.py|read|79]
[/Users/buildbot/buildarea/3.x.parc-leopard-1/build/Lib/asyncore.py|handle_read_event|435]
[/Users/buildbot/buildarea/3.x.parc-leopard-1/build/Lib/asynchat.py|handle_read|128]
[/Users/buildbot/buildarea/3.x.parc-leopard-1/build/Lib/asyncore.py|recv|375]
[/Users/buildbot/buildarea/3.x.parc-leopard-1/build/Lib/test/mock_socket.py|recv|47])
(...)

http://www.python.org/dev/buildbot/all/builders/PPC%20Leopard%203.x/builds/295

--
assignee: ronaldoussoren
components: Macintosh, Tests
keywords: buildbot
messages: 113971
nosy: flox, ronaldoussoren
priority: normal
severity: normal
status: open
title: buildbot: uncaptured python exception (smtpd), but no failure in regrtest
type: behavior
versions: Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8449] buildbot: test_dbm and test_dbm_ndbm failures on ia64 Ubuntu 3.1

[Florent Xicluna]

Florent Xicluna  added the comment:

No update on this issue, and there's no more ia64 buildbot.
There's very little chance to fix it.

--
components: +Tests
nosy: +flox
resolution:  -> out of date
status: open -> languishing
title: 
Now:
  buildbot: test_dbm and test_dbm_ndbm failures on ia64 Ubuntu 3.1
Was:
  buildbot: test_dbm and test_dbm_ndbm
  failures on ia64 Ubuntu 3.1
type:  -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8449] buildbot: test_dbm and test_dbm_ndbm failures on ia64 Ubuntu 3.1

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +doko

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5867] No way to create an abstract classmethod

[Antoine Pitrou]

Antoine Pitrou  added the comment:

The patch looks fine code-wise, but it also needs a doc addition in 
Doc/library/abc.rst.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9610] buildbot: uncaptured python exception (smtpd), but no failure in regrtest

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +richard

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9611] FileIO not 64-bit safe under Windows

[Antoine Pitrou]

New submission from Antoine Pitrou :

Modules/_io/fileio.c assumes that read() and write() allow a Py_ssize_t length, 
but under Windows the length is an int, limiting chunk size to 2GB.

It should be easy enough to read or write in multiple chunks, although testing 
might be difficult.

--
components: Extension Modules, Windows
messages: 113974
nosy: pitrou
priority: normal
severity: normal
status: open
title: FileIO not 64-bit safe under Windows
type: behavior
versions: Python 2.7, Python 3.1, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9566] Compilation warnings under x64 Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Created #9611 to report the FileIO 64-bit issue under Windows.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9612] setobject.c warnings under 64-bit Windows

[Antoine Pitrou]

New submission from Antoine Pitrou :

None of these warnings look critical (one affects the "search finger" 
optimization of pop(), one affects the result from __length_hint__ on set 
iterators, and the other the hash value of frozensets without any obviously bad 
consequences), but you might want to take a look at them anyway.

(for the record, a C "long" is 32-bit under 64-bit Windows, so a Py_ssize_t 
won't fit in it)

1>..\Objects\setobject.c(743) : warning C4244: '=' : conversion from 
'Py_ssize_t' to 'long', possible loss of data
1>..\Objects\setobject.c(772) : warning C4244: '*=' : conversion from 
'Py_ssize_t' to 'long', possible loss of data
1>..\Objects\setobject.c(819) : warning C4244: 'function' : conversion from 
'Py_ssize_t' to 'long', possible loss of data

--
assignee: rhettinger
components: Interpreter Core
messages: 113976
nosy: pitrou, rhettinger
priority: low
severity: normal
status: open
title: setobject.c warnings under 64-bit Windows
type: behavior
versions: Python 2.7, Python 3.1, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9566] Compilation warnings under x64 Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Created #9612 for the mostly harmless warnings in the set implementation.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9566] Compilation warnings under x64 Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

The zlib warnings are genuine and there's a specific bug for 64-bitness of 
zlibmodule.c: #8650.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7255] "Default" word boundaries for Unicode data?

[daniel mccloy]

daniel mccloy  added the comment:

Woo-HOOO!  Am very excited to hear this!  Thanks, Matthew!  This and also the 
related \w \W handling (#1693050) should be extremely useful for processing 
Indic text.  I'm a python newbie, so will need to find some help on what I need 
to do to compile/install/use this source-file download, but if I can figure 
that out, I'd be very happy to test this against a texts in a variety of Indic 
scripts.  Way to go!

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9611] FileIO not 64-bit safe under Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

os.write() (in posixmodule.c) is also affected. os.read(), however, is limited 
to 32-bit inputs.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8650] zlibmodule.c isn't 64-bit clean

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Using chunked writes is tricky. If the first write succeeds, and the second one 
fails, how do you report the result?

--
nosy: +loewis

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9613] Python considers pid longs under 64-bit Windows

[Antoine Pitrou]

New submission from Antoine Pitrou :

Under 64-bit Windows, Python aliases PyLong_FromPid() to PyLong_FromLong() (and 
PyLong_AsPid() to PyLong_AsLong()), but a C "long" is 32-bit, while apparently 
the MSVCRT defines a pid to be intptr_t, that is 64-bit. A potential loss of 
data ensues.

--
components: Extension Modules, Interpreter Core, Windows
messages: 113982
nosy: brian.curtin, pitrou, tim.golden
priority: normal
severity: normal
status: open
title: Python considers pid longs under 64-bit Windows
type: behavior
versions: Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9611] FileIO not 64-bit safe under Windows

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +brian.curtin, tim.golden

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9566] Compilation warnings under x64 Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Opened #9613 for 64-bitness of process ids.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9612] setobject.c warnings under 64-bit Windows

[Martin v . Löwis]

Martin v. Löwis  added the comment:

For the length hint, it would be best to use PyLong_FromSize_t, as in 
dictobject.c. It would be sad if __length_hint__ would return a much-too-small 
value (or even a negative number).

For the search finger, dictobject has opted to make me_hash of type Py_ssize_t.

--
nosy: +loewis

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9611] FileIO not 64-bit safe under Windows

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Using chunked writes is tricky. If the first write succeeds, and the second one 
fails, how do you report the result?

--
nosy: +loewis

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9614] _pickle is not entirely 64-bit safe

[Antoine Pitrou]

New submission from Antoine Pitrou :

A number of legitimate warnings get emitted under a 64-bit Windows build (in 
many places, _pickle uses ints or longs instead of "Py_ssize_t" variable to 
store various lengths and sizes):

1>..\Modules\_pickle.c(284) : warning C4244: '=' : conversion from 'Py_ssize_t' 
to 'int', possible loss of data
1>..\Modules\_pickle.c(301) : warning C4244: '=' : conversion from 'Py_ssize_t' 
to 'int', possible loss of data
1>..\Modules\_pickle.c(461) : warning C4244: '+=' : conversion from 
'Py_ssize_t' to 'int', possible loss of data
1>..\Modules\_pickle.c(628) : warning C4244: '=' : conversion from 'Py_ssize_t' 
to 'long', possible loss of data
1>..\Modules\_pickle.c(647) : warning C4267: '=' : conversion from 'size_t' to 
'int', possible loss of data
1>..\Modules\_pickle.c(1320) : warning C4244: '=' : conversion from 
'Py_ssize_t' to 'int', possible loss of data
1>..\Modules\_pickle.c(1558) : warning C4244: '=' : conversion from 
'Py_ssize_t' to 'int', possible loss of data
1>..\Modules\_pickle.c(1806) : warning C4244: '=' : conversion from 
'Py_ssize_t' to 'int', possible loss of data

--
components: Extension Modules
messages: 113986
nosy: alexandre.vassalotti, pitrou
priority: normal
severity: normal
status: open
title: _pickle is not entirely 64-bit safe
type: behavior
versions: Python 3.1, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8650] zlibmodule.c isn't 64-bit clean

[Martin v . Löwis]

Changes by Martin v. Löwis :


--
Removed message: http://bugs.python.org/msg113981

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9566] Compilation warnings under x64 Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Opened #9614 for the _pickle issues (which look quite legitimate).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9611] FileIO not 64-bit safe under Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

The write() man page says:

   The number of bytes written may be less than count if, for example, 
there is  insufficient  space  on
   the underlying physical medium, or the RLIMIT_FSIZE resource limit is 
encountered (see setrlimit(2)),
   or the call was interrupted by a signal handler after having written 
less  than  count  bytes.   (See
   also pipe(7).)

So, we could return the number of bytes successfully written, and let the next 
call fail.

Another possibility is to only write 2GB-1 and let the caller retry.
Most people use buffered I/O, and the buffered layer automatically retries.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6321] Reload Python modules when running programs

[Cherniavsky Beni]

Cherniavsky Beni  added the comment:

When you run a program using F5 in IDLE,
it completely restarts the underlying interpreter!
If you meant a different way of running, please elaborate.

(Exception: it uses the same interpreter if you're running "idle -n"; this 
commonly happens on Windows if you rightclick->Edit with IDLE... a .py file - 
just don't use that.)

--
nosy: +cben

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9611] FileIO not 64-bit safe under Windows

[Martin v . Löwis]

Martin v. Löwis  added the comment:

> Most people use buffered I/O, and the buffered layer automatically retries.

I see. I think this is already slightly problematic: if you send an
interrupt, it won't oblige. IMO, any such loop ought to be
interruptable.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9611] FileIO not 64-bit safe under Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> > Most people use buffered I/O, and the buffered layer automatically retries.
> 
> I see. I think this is already slightly problematic: if you send an
> interrupt, it won't oblige. IMO, any such loop ought to be
> interruptable.

Well, the loop stops when an error status is returned by the raw IO
layer. At that point, the buffered IO layer re-raises the error after a
bit of internal cleanup.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7676] IDLE shell shouldn't use TABs

[Cherniavsky Beni]

Cherniavsky Beni  added the comment:

This is almost a duplicate of http://bugs.python.org/issue1196946
(though the solution there took a different direction).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7255] "Default" word boundaries for Unicode data?

[Matthew Barnett]

Matthew Barnett  added the comment:

If you're on Windows (x86, 32-bit) then compilation isn't necessary - just use 
the appropriate _regex.pyd.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9611] FileIO not 64-bit safe under Windows

[Martin v . Löwis]

Martin v. Löwis  added the comment:

> Well, the loop stops when an error status is returned by the raw IO
> layer. At that point, the buffered IO layer re-raises the error after a
> bit of internal cleanup.

Assume the following case:
1. writing starts, and writes some data
2. Ctrl-C is pressed, raises a signal, and interrupts the current
   system call (EINTR)
3. having already written data, the signal is discarded, and the
   number of successfully written bytes is returned.
4. the loop retries to write the rest. Not receiving any signal
   anymore, the subsequent write operations wait for completion.

End consequence: the signal is discarded without any effect.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9587] unittest.assertRaises() return the raised exception

[Denver Coneybeare]

Denver Coneybeare  added the comment:

Michael: Do you disagree with assertRaises() returning the exception object on 
principle?  Or is this just the consensus that you got from the mailing list, 
including Guido's comment.  My particular use case is that I want to check 
certain attributes being set on the raised exception and I feel that the 
context manager approach is overkill for my tests since it's just one method 
call in the context manager.  I don't understand why it is considered "odd" for 
assertRaises() to return the result for further inspection... I need to get it 
some way and assertRaises() has a reference to it.  Thanks for considering this 
request further.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9612] setobject.c warnings under 64-bit Windows

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Antoine, thanks for posting these.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9611] FileIO not 64-bit safe under Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Le dimanche 15 août 2010 à 18:53 +, Martin v. Löwis a écrit :
> Martin v. Löwis  added the comment:
> 
> > Well, the loop stops when an error status is returned by the raw IO
> > layer. At that point, the buffered IO layer re-raises the error after a
> > bit of internal cleanup.
> 
> Assume the following case:
> 1. writing starts, and writes some data
> 2. Ctrl-C is pressed, raises a signal, and interrupts the current
>system call (EINTR)
> 3. having already written data, the signal is discarded, and the
>number of successfully written bytes is returned.
> 4. the loop retries to write the rest. Not receiving any signal
>anymore, the subsequent write operations wait for completion.

Ok, I guess the loop should run PyErr_CheckSignals() somewhere.

Simulate such a situation in an unit test will be a bit tricky.
Perhaps we can use os.pipe() and depend on the fact that writes greater
than the pipe buffer size will be blocking.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9615] Building SSL fails under 64-bit Windows

[Antoine Pitrou]

New submission from Antoine Pitrou :

This is what I get when MSVC 2008 tries to build the _ssl module:

8>-- Build started: Project: _ssl, Configuration: Debug x64 --
8>Performing Pre-Build Event...
8>'""' is not recognized as an internal or external command,
8>operable program or batch file.
8>Project : error PRJ0019: A tool returned an error code from "Performing 
Pre-Build Event..."
8>Build log was saved at 
"file://Z:\py3k\__svn__\PCbuild\x64-temp-Debug\_ssl\BuildLog.htm"
8>_ssl - 1 error(s), 0 warning(s)

The build log has the following contents:

Creating temporary file 
"C:\Users\Antoine\AppData\Local\Temp\BAT00012021242476.bat" with contents
[
@echo off

cd "Z:\py3k\__svn__\PCbuild\"

"" build_ssl.py Release x64 -a



if errorlevel 1 goto VCReportError

goto VCEnd

:VCReportError

echo Project : error PRJ0019: A tool returned an error code from "Performing 
Pre-Build Event..."

exit 1

:VCEnd
]
Creating command line 
"C:\Users\Antoine\AppData\Local\Temp\BAT00012021242476.bat"


I have installed Perl and Python 2.7.

--
components: Build, Extension Modules, Windows
messages: 113998
nosy: loewis, pitrou
priority: normal
severity: normal
status: open
title: Building SSL fails under 64-bit Windows
versions: Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9615] Building SSL fails under 64-bit Windows

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Try setting HOST_PYTHON.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9610] buildbot: uncaptured python exception (smtpd), but no failure in regrtest

[Ronald Oussoren]

Ronald Oussoren  added the comment:

Could this be related to Issue5154?

I've noticed in the past that some asyncore/asychat tests print stacktraces as 
well, all of them in the testcases that use poll instead of select.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9612] setobject.c warnings under 64-bit Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

There is also a similar warning for deque iterators' __length_hint__ (line 1124 
in _collectionsmodule.c).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9566] Compilation warnings under x64 Windows

[Brian Curtin]

Changes by Brian Curtin :


--
nosy: +brian.curtin

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9425] Rewrite import machinery to work with unicode paths

[STINNER Victor]

STINNER Victor  added the comment:

I tried to fix Mac OS X (TESTFN_UNENCODABLE) with r84035, but I don't have 
access to Mac OS X to test and my patch was not correct. It should now be ok 
with r84080.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5154] OSX broken poll testing doesn't work

[Florent Xicluna]

Florent Xicluna  added the comment:

Same issue, probably, on buildbot "PPC Tiger"

==
ERROR: test_main (test.test_signal.InterProcessSignalTests)
--
Traceback (most recent call last):
  File 
"/Users/buildbot/buildarea/3.1.parc-tiger-1/build/Lib/test/test_signal.py", 
line 156, in test_main
child = os.fork()
OSError: [Errno 35] Resource temporarily unavailable


http://www.python.org/dev/buildbot/all/builders/PPC%20Tiger%203.1/builds/246

And similar output on 2.6 and 3.x as well.

--
assignee:  -> ronaldoussoren
components: +Macintosh
keywords: +buildbot
nosy: +flox

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9615] Building SSL fails under 64-bit Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> Try setting HOST_PYTHON.

It worked, thank you.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8857] socket.getaddrinfo needs tests

[Ronald Oussoren]

Ronald Oussoren  added the comment:

I think there is a missing '0' in the failing line:

Index: Lib/test/test_socket.py
===
--- Lib/test/test_socket.py (revision 84079)
+++ Lib/test/test_socket.py (working copy)
@@ -608,7 +608,7 @@
 for _, socktype, _, _, _ in infos:
 self.assertEqual(socktype, socket.SOCK_STREAM)
 # test proto and flags arguments
-socket.getaddrinfo(HOST, None, 0, 0, socket.AI_CANONNAME)
+socket.getaddrinfo(HOST, None, 0, 0, 0, socket.AI_CANONNAME)
 socket.getaddrinfo(HOST, None, 0, 0, 0, socket.AI_PASSIVE)
 # a server willing to support both IPv4 and IPv6 will
 # usually do this



With this patch the tests pass, without the patch AI_CANNAME gets used as the 
value for 'proto'.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9601] ftplib should accept 250 on MKD

[alphablue52]

alphablue52  added the comment:

Yes.
If you send a "MKD" than Windows Server responses "250", and ftplib generates 
an Error.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9616] copy.deepcopy() copying pointers from a dict/dict/list, should copy values

[Neil Harkins]

New submission from Neil Harkins :

hi. after using deepcopy() on a nested dict/list structure, 
i noticed that modifications to the deepcopied structure were 
affecting the original. this looks to me like a serious bug:

>>> import copy
>>> foo = { 'a':[1,2,3], 'b':{'c':[4,5]} }
>>> bar = copy.deepcopy(foo)
>>> id(foo)
4297360512
>>> id(bar)
4297373104
>>> id(foo['a'])
4299410752
>>> id(bar['a'])
4299760200
>>> id(foo['b'])
4297371984
>>> id(bar['b'])
4297373920
>>> id(foo['b']['c'])
4299721040
>>> id(bar['b']['c'])
4299761496
>>> id(foo['b']['c'][0])
4297074656
>>> id(bar['b']['c'][0])
4297074656

--
components: Extension Modules
messages: 114007
nosy: nharkins
priority: normal
severity: normal
status: open
title: copy.deepcopy() copying pointers from a dict/dict/list, should copy 
values
type: behavior
versions: Python 2.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9616] copy.deepcopy() copying pointers from a dict/dict/list, should copy values

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Why do you say "modifications to the deepcopied structure were 
affecting the original"? Your code sample doesn't include any modifications to 
the deepcopied structure.

Try modifying it, and watch the original remaining unchanged.

--
nosy: +loewis

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9616] copy.deepcopy() copying pointers from a dict/dict/list, should copy values

[Neil Harkins]

Neil Harkins  added the comment:

thanks for the quick response. 

that was just my working up a simplified repro, but you are 
correct: on modification there, it gets a new id() location.

totally not what i would've expected (python flags
it for copying when it changes, to save space?)

however i am still seeing the problem in my code, so
i will continue to whittle it down to a simpler repro,
and hopefully add it here later today.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9616] copy.deepcopy() copying pointers from a dict/dict/list, should copy values

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Numbers are immutable, and hence don't need to be copied. In fact, it is 
impossible to create two int object that both have the value 4, but are 
different objects:

py> 2+2 is 3+1
True

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2889] curses for windows (alternative patch)

[ipatrol]

ipatrol  added the comment:

Any progress yat?

--
components: +Windows
nosy: +ipatrol
type:  -> feature request
versions: +Python 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9617] Buffered IO shouldn't ignore incoming signals during a partial write

[Antoine Pitrou]

New submission from Antoine Pitrou :

Prompted by Martin in #9611, here is a patch fixing the new buffered IO layer 
so that an incoming signal during a successful partial write() doesn't get 
ignored. Tests included.

--
components: IO
files: sigbufio.patch
keywords: patch
messages: 114012
nosy: exarkun, loewis, pitrou, rnk
priority: normal
severity: normal
stage: patch review
status: open
title: Buffered IO shouldn't ignore incoming signals during a partial write
type: behavior
versions: Python 2.7, Python 3.1, Python 3.2
Added file: http://bugs.python.org/file18540/sigbufio.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2889] curses for windows (alternative patch)

[Martin v . Löwis]

Martin v. Löwis  added the comment:

It can't go into 2.x anymore.

--
versions: +Python 3.2 -Python 2.6, Python 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9617] Buffered IO shouldn't ignore incoming signals during a partial write

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Another possibility is to do the check in the FileIO object instead. Both 
approaches give the same results for standard file descriptor IO.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9587] unittest.assertRaises() return the raised exception

[Michael Foord]

Michael Foord  added the comment:

Providing access to the exception on the context manager was *precisely* to 
meet the use case of wanting to make assertions about the exception. I tend to 
agree with Guido that having one of the asserts return something is a bit odd, 
but irrespective of that I don't think we should have two ways of doing exactly 
the same thing. 

In general I find that the with statement version of assertRaises looks a lot 
better than the old way of calling it, so I guess I also disagree that it is 
"overkill" or adds bloat.

Sorry guys.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9616] copy.deepcopy() copying pointers from a dict/dict/list, should copy values

[Neil Harkins]

Neil Harkins  added the comment:

learn something everyday. i have found the bug in my code, 
deepcopy() is not to blame. thx for your time!

--
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6321] Reload Python modules when running programs

[samwyse]

samwyse  added the comment:

As it happens, I do use Windows and almost exclusively start IDLE via 
right-clicks on .py files. I've never seen the behavior you describe documented 
anywhere.

On Aug 15, 2010, at 1:37 PM, Cherniavsky Beni  wrote:

> 
> Cherniavsky Beni  added the comment:
> 
> When you run a program using F5 in IDLE,
> it completely restarts the underlying interpreter!
> If you meant a different way of running, please elaborate.
> 
> (Exception: it uses the same interpreter if you're running "idle -n"; this 
> commonly happens on Windows if you rightclick->Edit with IDLE... a .py file - 
> just don't use that.)
> 
> --
> nosy: +cben
> 
> ___
> Python tracker 
> 
> ___

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9189] Improve CFLAGS handling

[Stefan Krah]

Stefan Krah  added the comment:

Starting with r82746 in py3k, I'm getting duplicate LDFLAGS in sysconfig:

make distclean
export BASECFLAGS="-ftest-coverage -fprofile-arcs"
export LDFLAGS="-fprofile-arcs"
./configure
make

$ ./python 
Python 3.2a0 (py3k:82746M, Aug 16 2010, 00:25:49) 
[GCC 4.1.3 20080623 (prerelease) (Ubuntu 4.1.2-23ubuntu3)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('LDFLAGS')
'-fprofile-arcs -fprofile-arcs'



test_sysconfig currently fails, so perhaps one of the duplicate flags
is mistakenly appended to LDFLAGS instead of LDSHARED:


$ ./python Lib/test/regrtest.py -uall test_sysconfig
[1/1] test_sysconfig
test test_sysconfig failed -- Traceback (most recent call last):
  File "/home/stefan/svn/py3k/Lib/test/test_sysconfig.py", line 285, in 
test_ldshared_value
self.assertIn(ldflags, ldshared)
AssertionError: '-fprofile-arcs -fprofile-arcs' not found in 'gcc -pthread 
-shared'

--
nosy: +skrah
resolution: fixed -> 
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9618] IDLE shell ignores all but first statement

[Cherniavsky Beni]

New submission from Cherniavsky Beni :

[Spinoff of http://bugs.python.org/issue3559]

If you manage to type several simple statements into the prompt (by 
copy-pasting them, using Ctrl+J, or creative deletion), IDLE runs the first one 
and silently ignores the rest:

>>> x = 1
x = 2
>>> x
1

Moreover, it doesn't even parse the additional lines:

>>> x = 3
$...@syntax error?!
>>> x
3

If the first statement is a compound statement, IDLE refuses with a SyntaxError 
at the begging of the second statement:


>>> def f():
return 42
f()
SyntaxError: invalid syntax


I believe in both cases the right least-surprise behavior is to run all 
statements.

If not, a clear error explaining that IDLE doesn't support multiple statements 
must be printed.  But I can't see a reason to choose this over making it Just 
Work.


[Implementation: might or might not be related to 
http://bugs.python.org/issue7741]

--
components: IDLE
messages: 114019
nosy: cben
priority: normal
severity: normal
status: open
title: IDLE shell ignores all but first statement
versions: Python 2.7, Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9582] documentation line needs rewording

[Terry J. Reedy]

Terry J. Reedy  added the comment:

PATCH add 'are' after 'expressions'.

--
keywords: +patch
nosy: +terry.reedy
stage:  -> needs patch
type:  -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9582] documentation line needs rewording

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
keywords: +easy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9583] PYTHONOPTIMIZE = 0 is not honored

[Terry J. Reedy]

Terry J. Reedy  added the comment:

How did you conclude that PYTHONOPTIMIZE = 0 is not honored? Can you provide a 
minimal example or demonstration.

In any case, 2.6.6 is nearly out so bad behavior needs to be demonstrated with 
2.7/3.x.

--
nosy: +terry.reedy
versions: +Python 2.7, Python 3.2 -Python 2.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3559] Pasted \n not same as typed \n

[Cherniavsky Beni]

Cherniavsky Beni  added the comment:

There are 2 issues here:

(1) There should be a quick & obvious way to paste and run several statements.

(2) If a user types several statements and presses Enter, all should run.  The 
current behavior is badly broken, and pasting is just one of the ways to 
trigger this.  Splitting this into a new bug: http://bugs.python.org/issue9618

The original formulation of this bug seems to favor an xterm-like solution to 
(1): when you paste \n-terminated, run them immediately, as if each \n was an 
Enter press.

I think a more IDLEic [think "idillic" ;-)] approach to solving (1) is to solve 
(2): keep the behavior that pasting creates a multi-line block without 
executing anything, make Enter execute it all.  Benefits:

- More intuitive to users that have never pasted multiple lines into a shell 
terminal.
- More sensible: why should Pasting execute anything?!
- Allows editing any of the statements before running.
- Keeps all statements together for Alt+P recalling.

If there is agreement on this, then this issue requires no action beyond 
solving issue 9618.

--
nosy: +cben

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9562] Slightly misleading wording in documentation of dict.update

[Terry J. Reedy]

Terry J. Reedy  added the comment:

I agree with the replacement: 'tuples' and 'interables' modify and must agree 
with 'pairs', not the initial 'iterable'.

--
keywords: +easy, patch
nosy: +terry.reedy
stage:  -> needs patch
versions: +Python 3.2 -Python 2.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9619] test_ssl freezes

[Antoine Pitrou]

New submission from Antoine Pitrou :

Recently there have been test_ssl freezes on the buildbots. They seem to happen 
in the asyncore test case:

http://www.python.org/dev/buildbot/builders/i386%20Ubuntu%203.x/builds/1903/steps/test/logs/stdio
http://www.python.org/dev/buildbot/builders/x86%20Ubuntu%203.x/builds/1742/steps/test/logs/stdio

test_asyncore_server (test.test_ssl.ThreadedTests)
Check the example asyncore integration. ... 
 server:  new connection from 127.0.0.1:36622
 client:  sending b'FOO\n'...
 server:  read b'FOO\n' from client
 client:  read b'foo\n'
 client:  closing connection.
 server:  read b'over\n' from client
 server:  closed connection 
 server:  read b'' from client


The only significant change recently in ssl has been r83869, and asyncore 
doesn't seem to have recent any important changes lately.

--
components: Library (Lib), Tests
messages: 114024
nosy: giampaolo.rodola, pitrou
priority: normal
severity: normal
status: open
title: test_ssl freezes
versions: Python 3.2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9533] metaclass can't derive from ABC

[Terry J. Reedy]

Terry J. Reedy  added the comment:

+- same traceback in 3.1
Since ABCmeta is not used (by name) its import is not needed.
I have no opinion on whether this should work.

--
nosy: +terry.reedy
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9523] Improve dbm module

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Upgrading to match the MutableMapping interface seems reasonable.

--
nosy: +terry.reedy
stage:  -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9582] documentation line needs rewording

[Éric Araujo]

Éric Araujo  added the comment:

+1 on committing this change.

--
nosy: +eric.araujo

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8491] Need readline command and keybinding information

[Mitchell Model]

Mitchell Model  added the comment:

On Aug 5, 2010, at 3:48 PM, Terry J. Reedy wrote:

> 
> Terry J. Reedy  added the comment:
> 
> Can you suggest a specific link and a specific location where to add it?

I would add a sentence to the first paragraph of the readline doc:

Readline keybindings may be configured via an initialization file, 
typically .inputrc in your home directory; see 
http://cnswww.cns.cwru.edu/php/chet/readline/readline.html#SEC9 (or 
http://www.gnu.org/software/bash/manual/html_node/Readline-Init-File.html) for 
information about the format and allowable constructs of that file and the 
capabilities of the readline library in general.

I did a few quick tests and convinced myself that the module's C code's call to 
rl_initialize actually reads .inputrc (or the value of the environment variable 
INPUTRC if that is set).

> 
> --
> assignee: georg.brandl -> d...@python
> nosy: +d...@python, terry.reedy
> versions:  -Python 2.6
> 
> ___
> Python tracker 
> 
> ___

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9619] test_ssl freezes

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Actually, this can be reproduced by running test_smtpd before test_ssl:

$ ./python -m test.regrtest -v -uall test_smtpd test_ssl

It then freezes at that point:

[...]
test_asyncore_server (test.test_ssl.ThreadedTests)
Check the example asyncore integration. ... 
 server:  new connection from 127.0.0.1:46707
 client:  sending b'FOO\n'...
 server:  read b'FOO\n' from client
 client:  read b'foo\n'
 client:  closing connection.
 server:  read b'over\n' from client
 client:  connection closed.
 cleanup: stopping server.
 cleanup: joining server thread.
 server:  closed connection 
 server:  read b'' from client

If you press the return key, it unfreezes the test (does test_smtpd register 
file descriptor 0 (stdin) in asyncore?) and prints the following error:

error: uncaptured python exception, closing channel  (:pop from empty list 
[/home/antoine/py3k/debug/Lib/asyncore.py|read|79] 
[/home/antoine/py3k/debug/Lib/asyncore.py|handle_read_event|435] 
[/home/antoine/py3k/debug/Lib/asynchat.py|handle_read|128] 
[/home/antoine/py3k/debug/Lib/asyncore.py|recv|375] 
[/home/antoine/py3k/debug/Lib/test/mock_socket.py|recv|47])

--
nosy: +richard

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9619] test_ssl freezes

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> does test_smtpd register file descriptor 0 (stdin) in asyncore?

After some debug prints, it turns out to be the case.
One general problem is asyncore's global socket_map, which means it can leak 
between tests if some tests fail cleaning correctly after themselves.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9619] test_ssl freezes

[Antoine Pitrou]

Antoine Pitrou  added the comment:

In r84086, I've added a save/restore guard of asyncore.socket_map to the 
regression test suite. It also warns when a test fails to leave the socket_map 
in its initial test. test_smtpd is the only test that displays the warning.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6321] Reload Python modules when running programs

[Cherniavsky Beni]

Cherniavsky Beni  added the comment:

> As it happens, I do use Windows and almost exclusively start IDLE via 
> right-clicks on .py files. I've never seen the behavior you describe 
> documented anywhere.

You're right, it wasn't.
[IDLE does show a " No Subprocess " line in the IDLE shell when you 
launch it this way.  Unfortunately, the significance of this (and of the 
absence of "== Restart ==" lines on F5) wouldn't be obvious unless you 
followed IDLE development around 2.3... :-(]

If you're using Python up to 2.6/3.0, please fall back to starting IDLE from 
the Start menu → Programs → Python X.Y → IDLE, then use File→Open to open files.

Or upgrade to Python 2.7/3.1, where right click → Edit with IDLE was fixed 
[issue5847] to open IDLE in the fully-functional mode.  Note however, that once 
you have an open IDLE, still want to use File→Open or you'll get *2* IDLEs 
running at once, each with its own shell.

In both cases you'll notice IDLE will *completely* restart the underlying 
Python each time you press F5.  This eliminates any stale-module problems, but 
kills all variables and state you had; this might require a change of habits 
but in my experience it's well worth it.

[P.S. If you absolutely must have module reloading without killing the whole 
state, and you're willing to debug occasional issues, take a look at 
http://www.cherrypy.org/attachment/wiki/AutoReload/autoreload.py
and possibly http://www.codexon.com/posts/a-better-python-reload]

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com