[issue15360] Behavior of assigning to __dict__ is not documented

[Chris Rebert]

Changes by Chris Rebert :


--
nosy: +cvrebert

___
Python tracker 

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

[issue15269] Document dircmp.left and dircmp.right

[Eli Bendersky]

Eli Bendersky  added the comment:

I think it can go into 3.3 but only if it gets reviewed by another core dev 
(we're in release candidate stage now). Senthil - can you review the patch 
together with me?

As for customizing the stream, yes, go ahead and open a new issue for it, and 
add me there as nosy.

--

___
Python tracker 

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

[issue15436] __sizeof__ is not documented

[Chris Rebert]

Changes by Chris Rebert :


--
nosy: +cvrebert

___
Python tracker 

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

[issue14330] don't use host python, use host search paths for host compiler

[Georg Brandl]

Changes by Georg Brandl :


--
priority: normal -> release blocker

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

> +# The size of 'PyStructObject'
> +totalsize = size(self.header + '5P')

What if use totalsize = object.__sizeof__(struct_obj) ?

--

___
Python tracker 

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

[issue15368] bytecode generation is not deterministic

[Eric Snow]

Changes by Eric Snow :


--
nosy: +eric.snow

___
Python tracker 

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

[issue14578] importlib doesn't check Windows registry for paths

[Eric Snow]

Eric Snow  added the comment:

Brian, perhaps the problem described in issue15431 ("Cannot build importlib.h 
on Windows") is part of the problem for you here.

--

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Martin v . Löwis]

Martin v. Löwis  added the comment:

issue15402-redux-v1.patch LGTM.

--

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Martin v . Löwis]

Martin v. Löwis  added the comment:

> So the good old "int main(void)" behaviour is "undefined" :-)

No, it's not; see 5.1.2.2.1p1.

--

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

> Talking about this, anybody has an electronic version of C Standard to
> share with me, or should I hunt around the dark corners of Internet? :-)

http://www.open-std.org/jtc1/sc22/wg14/www/standards (see n1256.pdf).

--

___
Python tracker 

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

[issue14201] Documented caching for shared library's __getattr__ and __getitem__ is incorrect

[Meador Inge]

Meador Inge  added the comment:

Any comments on this one?  I plan on committing the changes tomorrow unless I 
hear something otherwise.

--

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Meador Inge]

Meador Inge  added the comment:

The attached patch fixes: (1) the test cases to make them exact (inspired by 
'test_sys.py'), (2) the definition of 's_sizeof' to add the dummy parameter, 
and (3) simplifies the sizeof calculation using 's_len'.

--
Added file: http://bugs.python.org/file26520/issue15402-redux-v1.patch

___
Python tracker 

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

[issue15452] Eliminate the use of eval() in the logging config implementation

[Arfrever Frehtes Taifersar Arahesis]

Changes by Arfrever Frehtes Taifersar Arahesis :


--
nosy: +Arfrever

___
Python tracker 

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

[issue10654] test_datetime sometimes fails on Python3.x windows binary

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Both subclasses return NotImplemented for d+1. Otherwise, TypeError or 
NotImplemented as expected. See file.

--
Added file: http://bugs.python.org/file26519/datetimetest.py

___
Python tracker 

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

[issue15415] Add temp_dir() and change_cwd() to test.support

[Nick Coghlan]

Changes by Nick Coghlan :


--
assignee:  -> ncoghlan
nosy: +ncoghlan

___
Python tracker 

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

[issue15441] test_posixpath fails on Japanese edition of Windows

[Atsuo Ishimoto]

Atsuo Ishimoto  added the comment:

Updated patch again.

In this patch, byte object is passed as argument to WindowsError as Victor's 
patch.

I prefer to fix PyErr_SetFromWindowsErrWithFilename() over path_error(), 
because PyErr_SetFromWindowsErrWithFilename() is public API, so someone may use 
PyErr_SetFromWindowsErrWithFilename() for their own extension modules.

--
Added file: http://bugs.python.org/file26518/issue15441_3.patch

___
Python tracker 

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

[issue15403] Refactor package creation support code into a common location

[Nick Coghlan]

Changes by Nick Coghlan :


--
assignee:  -> ncoghlan

___
Python tracker 

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

[issue10654] test_datetime sometimes fails on Python3.x windows binary

[Nick Coghlan]

Nick Coghlan  added the comment:

The precedence problems described in #11477 shouldn't factor into this case - 
that issue is specific to C level types that implement + and * via 
tp_as_sequence *without* implementing the corresponding slots in tp_as_number. 
That's not the case here, since datetime types *only* implement the slots via 
tp_as_number.

I can't reproduce the failure at all, so here's a couple of tricks for Windows 
users trying to reproduce or investigate the problem:

# Getting the C version of datetime:
import _datetime as cdt

# Getting the pure Python version of datetime:
from test.support import import_fresh_module
pydt = import_fresh_module("datetime", blocked=["_datetime"])

# Test the results of all the following operations
d+1
1+d
d.__add__(1)
d.__radd__(1)
1 .__add__(d)
1 .__radd__(d)

# For the following kinds of "d"
d = cdt.datetime(1, 2, 3)
d = pydt.datetime(1, 2, 3)
class SubC(cdt.datetime): pass
d = SubC(1, 2, 3)
class SubPy(cdt.datetime): pass
d = SubPy(1, 2, 3)

--
components: +Interpreter Core -Library (Lib)

___
Python tracker 

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

[issue15376] Refactor the test_runpy walk_package support code into a common location

[Chris Jerdonek]

Chris Jerdonek  added the comment:

Hi Nick, I was wondering if you'd have time to take a look at the patches I've 
uploaded to issue 15403 and issue 15415 at some point.

Once those are addressed, I think we will be in a much better position to 
address most of this issue.

--

___
Python tracker 

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

[issue10654] test_datetime sometimes fails on Python3.x windows binary

[Terry J. Reedy]

Terry J. Reedy  added the comment:

I do not see the error with installed 3.2.3. I **DO** see it consistently, when 
running the test with installed 3.3.0b1 on 64 bit Win 7. The only failure is
==
FAIL: test_computations (test.datetimetester.TestSubclassDateTime_Fast)
--
Traceback (most recent call last):
  File "C:\Programs\Python33\lib\test\datetimetester.py", line 1640, in 
test_computations
self.assertRaises(TypeError, lambda: a+i)
AssertionError: TypeError not raised by 
ionError: TypeError not raised by 

The other 9 runs of test_computations pass.
test_computations (test.datetimetester.TestDate_Pure) ... ok
test_computations (test.datetimetester.TestDateTimeTZ_Pure) ... ok
test_computations (test.datetimetester.TestTimeDelta_Pure) ... ok
test_computations (test.datetimetester.TestSubclassDateTime_Pure) ... ok
test_computations (test.datetimetester.TestDateTime_Pure) ... ok
test_computations (test.datetimetester.TestDate_Fast) ... ok
test_computations (test.datetimetester.TestDateTimeTZ_Fast) ... ok
test_computations (test.datetimetester.TestTimeDelta_Fast) ... ok
test_computations (test.datetimetester.TestDateTime_Fast) ... ok

I reproduce in same way Hirokazo does.
>>> class Sub(datetime): pass

>>> dsub = Sub(2002, 1, 31)
>>> dsub+1
NotImplemented
>>> d = datetime(2000,1,1)
>>> d+1
Traceback (most recent call last):
  File "", line 1, in 
b+1
TypeError: unsupported operand type(s) for +: 'datetime.datetime' and 'int'

My understanding of a+b is that a.__add__(b) is tried and if it NotImplemented, 
which d and dsub.__add__(1) do, b.__radd__(a) is tried. If that does the same, 
TypeError is raised. 1 .__radd__(x) returns NotImplemented for both d and dsub, 
but TypeError is raised only for d, not dsub.

Alexander, there are known problems with abstract.c #11477

Nick, I nosied you because you have worked on the binary op dance. Are there 
special problems for Python subclasses of builtins? Is this problem the same or 
related to the one in #11477?

--
nosy: +ncoghlan, terry.reedy
stage:  -> needs patch
title: test_datetime fails on Python3.2 windows binary -> test_datetime 
sometimes fails on Python3.x windows binary
versions: +Python 3.3

___
Python tracker 

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

[issue15452] Eliminate the use of eval() in the logging config implementation

[Nick Coghlan]

New submission from Nick Coghlan :

The current implementation of PEP 391 relies on eval, which is substantially 
more permissive than the expected syntax described in the spec. This means the 
listen() feature provides an attack vector for injection of untrusted code.

While the documentation has been updated with a cautionary note to this effect, 
longer term, the use of eval() should be replaced with:

1. ast.literal_eval()
2. refactoring the str.format attribute and item lookup code into something 
suitable for reuse in other contexts (perhaps exposed via the ast module as 
"ast.lookup_eval()")

--
components: Library (Lib)
messages: 166448
nosy: ncoghlan, vinay.sajip
priority: normal
severity: normal
stage: needs patch
status: open
title: Eliminate the use of eval() in the logging config implementation
type: security
versions: Python 3.4

___
Python tracker 

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

[issue15451] PATH is not honored in subprocess.Popen in win32

[Grissiom Gu]

New submission from Grissiom Gu :

My system is 32 bit win7 and python is 2.7.2.

Sample code is here:
===
import os, sys

nenv = {}
nenv['PATH'] = 'C:\\Windows\\System32\\;e:\\projects\\teest\\python\\exe\\'
nenv['SystemRoot'] = 'C:\\Windows\\'

#os.putenv('PATH', nenv['PATH'])
import subprocess
proc = subprocess.Popen('test.bat', stdin=subprocess.PIPE, 
stdout=subprocess.PIPE,
stderr=subprocess.PIPE, shell = False, env=nenv)
data, err = proc.communicate()
rv = proc.wait()

if data:
print data
if err:
print err
sys.exit(rv)
==
in E:\projects\teest\python I have two folders: 'exe/' have a bat file named 
'test.bat' and a 'launch/' folder have the above script. When execute the above 
script, python yield "WindowsError: [Error 2]" which means could not find the 
executable.

However, if I un-comment the line "#os.putenv('PATH', nenv['PATH'])", it works 
like a charm. It seems _subprocess.CreateProcess does not honer the PATH.

FYI, if I use the CreateProcess of win32 extensions, thing works fine without 
the need to export PATH.

--
messages: 166447
nosy: Grissiom.Gu
priority: normal
severity: normal
status: open
title: PATH is not honored in subprocess.Popen in win32
type: behavior
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

[issue15441] test_posixpath fails on Japanese edition of Windows

[Atsuo Ishimoto]

Atsuo Ishimoto  added the comment:

martin: while os.mkdir(b'\xe7w\xf0') succeeds, but strangely enough, subsequent 
os.chdir(b'\xe7w\xf0') fails.

This is not a bug in Python, but Windows issue.

--

___
Python tracker 

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

[issue15441] test_posixpath fails on Japanese edition of Windows

[Atsuo Ishimoto]

Atsuo Ishimoto  added the comment:

Here's another try:

In this patch:

- skip test_nonascii_abspath() test since it fails on some code pages.

- Added a test to reproduce bug on latin code pages.

- Use repr(filename) only if decode failed. This is more backward-compatible 
and does not lose any information.

--
Added file: http://bugs.python.org/file26517/issue15441_2.patch

___
Python tracker 

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

[issue14501] Error initialising BaseManager class with 'authkey' argument of string type.

[Richard Oudkerk]

Changes by Richard Oudkerk :


--
nosy: +sbt

___
Python tracker 

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

[issue14330] don't use host python, use host search paths for host compiler

[Ezio Melotti]

Ezio Melotti  added the comment:

The last changeset (7955d769fdf5) caused some problem on my machine.
Before the changeset I was getting:

Python build finished, but the necessary bits to build these modules were not 
found:
_bz2   _curses_curses_panel   
_dbm   _gdbm  _lzma   
_tkinter  
To find the necessary bits, look in setup.py in detect_modules() for the 
module's name.

After 7955d769fdf5 I get:

Python build finished, but the necessary bits to build these modules were not 
found:
_bz2   _curses_curses_panel   
_dbm   _gdbm  _lzma   
_sqlite3   _ssl   _tkinter
readline   zlib   
To find the necessary bits, look in setup.py in detect_modules() for the 
module's name.

I'm on an ubuntu 12.04 machine.

--
nosy: +ezio.melotti
status: closed -> open

___
Python tracker 

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

[issue15450] Allow dircmp.subdirs to behave well under subclassing

[Chris Jerdonek]

New submission from Chris Jerdonek :

Currently, the subdirs attribute of filecmp.dircmp does not respect subclassing:

>>> from filecmp import dircmp
>>> class MyDirCmp(dircmp):
...   pass
... 
>>> my_dcmp = MyDirCmp('dir1', 'dir2')
>>> for item in my_dcmp.subdirs.values():
...   print(type(item))
...   break
... 


This is the only place where dircmp does not respect subclassing.  It can be 
corrected here:

def phase4(self): # Find out differences between common subdirectories
...
...
self.subdirs[x]  = dircmp(a_x, b_x, self.ignore, self.hide)

This would let one do things like override dircmp.report() and have 
dircmp.report_full_closure() behave as expected.

--
components: Library (Lib)
keywords: easy
messages: 166443
nosy: cjerdonek
priority: normal
severity: normal
status: open
title: Allow dircmp.subdirs to behave well under subclassing
type: enhancement
versions: Python 3.4

___
Python tracker 

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

[issue15269] Document dircmp.left and dircmp.right

[Chris Jerdonek]

Chris Jerdonek  added the comment:

Attaching a patch to address Eli's requests (1) and (2).

Since this patch merely adds documentation and tests for existing 
functionality, is there any reason why this cannot go into Python 3.3?  Thanks.

--
Added file: http://bugs.python.org/file26516/issue-15269-2.patch

___
Python tracker 

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

[issue15441] test_posixpath fails on Japanese edition of Windows

[STINNER Victor]

STINNER Victor  added the comment:

> haypo: how is this meant to fix the bug?
> Won't it now cause a WindowsError, when a successful
> operation is expected?

Oh, I was referring to the new test proposed in the attached patch 
(issue15441.patch):

+def test_chdir_invalid_filename(self):
+self.assertRaises(WindowsError, os.chdir, b'\xe7w\xf0')

os.chdir() in a non existent directory with a bytes name should raise an 
OSError, not a UnicodeDecodeError.

--

About the original issue: it looks like mkdir(bytes) decodes internally the 
directory name and ignore undecodable bytes. On Windows 7, mkdir(b"\xe7w\xf0") 
creates a directory called "\u8f42" (b"\xe7w", b"\xf0" suffix has been 
dropped). It is not possible to change the directory to "b"\xe7w\xf0", but it 
works with "b"\xe7w" or "\u8f42".

There are 2 issues:

 * On Windows, os.chdir(bytes) should not raise a UnicodeDecodeError on the 
directory does not exist
 * test_nonascii_abspath() can be skipped on Windows if 
os.fsdecode(b"\xe7w\xf0") fails, or b"\xe7w" name should be used instead

My patch is not the best solution because it looses information (if the 
filename contains undecodable bytes). I realized that OSError.filename is not 
necessary a str, bytes is also accepted. win32_error_object() can be used. The 
following patch pass the original bytes object to OSError constructor instead:


diff -r 43ae2a243eca Modules/posixmodule.c
--- a/Modules/posixmodule.c Thu Jul 26 00:47:15 2012 +0200
+++ b/Modules/posixmodule.c Thu Jul 26 01:19:14 2012 +0200
@@ -1138,11 +1138,10 @@ static PyObject *
 path_error(char *function_name, path_t *path)
 {
 #ifdef MS_WINDOWS
-if (path->narrow)
-return win32_error(function_name, path->narrow);
-if (path->wide)
-return win32_error_unicode(function_name, path->wide);
-return win32_error(function_name, NULL);
+return PyErr_SetExcFromWindowsErrWithFilenameObject(
+PyExc_OSError,
+0,
+path->object);
 #else
 return path_posix_error(function_name, path);
 #endif

(sorry, I failed to attach a patch, I have an issue with my file chooser...)

--

___
Python tracker 

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

[issue15008] PEP 362 "Signature Objects" reference implementation

[Yury Selivanov]

Yury Selivanov  added the comment:

Benjamin: http://bugs.python.org/issue15151

--
nosy: +yselivanov

___
Python tracker 

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

[issue15436] __sizeof__ is not documented

[Antoine Pitrou]

Antoine Pitrou  added the comment:

sys.getsizeof() is not for production code, it's for experimenting and getting 
information at the command prompt. It's quite useful when you know its 
limitations.

I'd argue that implementing __sizeof__ for user types doesn't make much sense 
(except C extension types, which are CPython-specific).

--
nosy: +pitrou

___
Python tracker 

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

[issue15436] __sizeof__ is not documented

[Raymond Hettinger]

Raymond Hettinger  added the comment:

This may be CPython specific.

Also, sys.getsizeof() hasn't proved to be very useful (I never see anyone use 
it or see it in production code).  Worse, it doesn't even make sense in the 
case of shared-key dictionaries and whatnot.  Accordingly, there is little 
reason to make this more public than it already is.  I would be happy to see it 
written-off as an implementation detail.

--
nosy: +rhettinger

___
Python tracker 

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

[issue13538] Improve doc for str(bytesobject)

[Ezio Melotti]

Changes by Ezio Melotti :


--
keywords: +easy
stage:  -> needs patch
type:  -> enhancement

___
Python tracker 

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

[issue15320] thread-safety issue in regrtest.main()

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Ok, I've committed the patch to 3.2 and 3.3. I don't really want to bother with 
2.7 (it's a rare enough issue). Thank you Chris!

--
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed
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

[issue15320] thread-safety issue in regrtest.main()

[Roundup Robot]

Roundup Robot  added the comment:

New changeset d7a64e095930 by Antoine Pitrou in branch '3.2':
Issue #15320: Make iterating the list of tests thread-safe when running tests 
in multiprocess mode.
http://hg.python.org/cpython/rev/d7a64e095930

New changeset 43ae2a243eca by Antoine Pitrou in branch 'default':
Issue #15320: Make iterating the list of tests thread-safe when running tests 
in multiprocess mode.
http://hg.python.org/cpython/rev/43ae2a243eca

--
nosy: +python-dev

___
Python tracker 

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

[issue4712] Document pickle behavior for subclasses of dicts/lists

[Ezio Melotti]

Changes by Ezio Melotti :


--
versions: +Python 3.2, Python 3.3, Python 3.4 -Python 2.6, Python 3.0, Python 
3.1

___
Python tracker 

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

[issue14501] Error initialising BaseManager class with 'authkey' argument of string type.

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +jnoller
stage:  -> needs patch

___
Python tracker 

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

[issue13525] Tutorial: Example of Source Code Encoding triggers error

[Ezio Melotti]

Changes by Ezio Melotti :


--
type:  -> enhancement

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Meador Inge]

Meador Inge  added the comment:

On Wed, Jul 25, 2012 at 5:38 PM, Jesús Cea Avión  wrote:

> So the good old "int main(void)" behaviour is "undefined" :-)

Actually the C Standard says that is OK.  See 5.1.2.2.1 of ISO/IEC 9899:TC3.

--

___
Python tracker 

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

[issue7593] Computed-goto patch for RE engine

[Ezio Melotti]

Changes by Ezio Melotti :


--
versions: +Python 3.4 -Python 3.2

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Jesús Cea Avión]

Jesús Cea Avión  added the comment:

Talking about this, anybody has an electronic version of C Standard to share 
with me, or should I hunt around the dark corners of Internet? :-)

--

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Jesús Cea Avión]

Jesús Cea Avión  added the comment:

So the good old "int main(void)" behaviour is "undefined" :-)

--

___
Python tracker 

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

[issue15320] thread-safety issue in regrtest.main()

[Chris Jerdonek]

Chris Jerdonek  added the comment:

Thanks, Antoine. Just a note: with that other implementation I think the call 
to pending.close() would probably also warrant a lock since it appears close() 
can't be called either if a generator is already executing (granted that 
situation would be even rarer since it could arise only during 
KeyboardInterrupt).

--

___
Python tracker 

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

[issue15008] PEP 362 "Signature Objects" reference implementation

[Benjamin Peterson]

Benjamin Peterson  added the comment:

Are we going to get documentation?

--
nosy: +benjamin.peterson

___
Python tracker 

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

[issue15441] test_posixpath fails on Japanese edition of Windows

[Martin v . Löwis]

Martin v. Löwis  added the comment:

haypo: how is this meant to fix the bug? Won't it now cause a WindowsError, 
when a successful operation is expected?

--

___
Python tracker 

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

[issue15441] test_posixpath fails on Japanese edition of Windows

[STINNER Victor]

STINNER Victor  added the comment:

decode_filename_mbcs.patch uses the "replace" error handler to decode
the filename on Windows. It should solve the issue.

--
Added file: http://bugs.python.org/file26515/decode_filename_mbcs.patch

___
Python tracker 

___diff -r b127046831e2 Python/errors.c
--- a/Python/errors.c   Mon Jul 23 00:24:24 2012 -0500
+++ b/Python/errors.c   Wed Jul 25 15:40:52 2012 +0200
@@ -463,11 +463,22 @@ PyErr_SetFromErrnoWithFilenameObject(PyO
 return NULL;
 }
 
+static PyObject *
+decode_filename(const char *filename)
+{
+if (!filename)
+return NULL;
+#ifdef HAVE_MBCS
+return PyUnicode_DecodeMBCS(filename, strlen(filename), "replace");
+#else
+return PyUnicode_DecodeFSDefault(filename);
+#endif
+}
 
 PyObject *
 PyErr_SetFromErrnoWithFilename(PyObject *exc, const char *filename)
 {
-PyObject *name = filename ? PyUnicode_DecodeFSDefault(filename) : NULL;
+PyObject *name = decode_filename(filename);
 PyObject *result = PyErr_SetFromErrnoWithFilenameObject(exc, name);
 Py_XDECREF(name);
 return result;
@@ -558,7 +569,7 @@ PyObject *PyErr_SetExcFromWindowsErrWith
 int ierr,
 const char *filename)
 {
-PyObject *name = filename ? PyUnicode_DecodeFSDefault(filename) : NULL;
+PyObject *name = decode_filename(filename);
 PyObject *ret = PyErr_SetExcFromWindowsErrWithFilenameObject(exc,
  ierr,
  name);
@@ -595,7 +606,7 @@ PyObject *PyErr_SetFromWindowsErrWithFil
 int ierr,
 const char *filename)
 {
-PyObject *name = filename ? PyUnicode_DecodeFSDefault(filename) : NULL;
+PyObject *name = decode_filename(filename);
 PyObject *result = PyErr_SetExcFromWindowsErrWithFilenameObject(
   PyExc_WindowsError,
   ierr, name);
@@ -892,7 +903,7 @@ PyErr_SyntaxLocationEx(const char *filen
 }
 }
 if (filename != NULL) {
-tmp = PyUnicode_DecodeFSDefault(filename);
+tmp = decode_filename(filename);
 if (tmp == NULL)
 PyErr_Clear();
 else {
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15209] Re-raising exceptions from an expression

[Tyler Crompton]

Tyler Crompton  added the comment:

As for the losing valuable debug information, much worse can be done:

import sys

try:
x
except NameError:
print('An error occurred.', file=sys.stderr)
sys.exit(1)

This is obviously not how one should handle errors in development, but it's 
allowed. As Ethan pointed out, the initial proposal can be recreated by just 
adding three words which is obviously also allowed.

Nick, I'm not saying you're opinions are wrong, I just wanted to point out how 
easy it is to throw away valuable information. It's almost futile.

--

___
Python tracker 

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

[issue15320] thread-safety issue in regrtest.main()

[Antoine Pitrou]

Antoine Pitrou  added the comment:

I would have taken the "simpler" route myself (taking the lock around the 
next() call), that said it looks ok as it is to me. Do other people have an 
opinion?

--

___
Python tracker 

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

[issue15320] thread-safety issue in regrtest.main()

[Chris Jerdonek]

Chris Jerdonek  added the comment:

Antoine, does the latest patch look okay to you, or did you want something even 
more minimal (e.g. by defining and acquiring the lock directly in main)?

--

___
Python tracker 

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

[issue15431] Cannot build importlib.h on Windows

[Kristján Valur Jónsson]

Kristján Valur Jónsson  added the comment:

shouldn't be too hard to add, I'll give it a go soon.

--

___
Python tracker 

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

[issue15449] Optional size argument for readline()

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
resolution:  -> works for me
status: open -> closed

___
Python tracker 

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

[issue15449] Optional size argument for readline()

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Well, it does:
http://docs.python.org/dev/library/io.html#io.IOBase.readline

“readline(limit=-1)

Read and return one line from the stream. If limit is specified, at most 
limit bytes will be read.”

--
nosy: +pitrou

___
Python tracker 

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

[issue15431] Cannot build importlib.h on Windows

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +kristjan.jonsson, sbt

___
Python tracker 

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

[issue12605] Enhancements to gdb 7 debugging hooks

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Dave, test_gdb fails consistently on the ARM buildbot:


==
FAIL: test_threads (test.test_gdb.PyBtTests)
Verify that "py-bt" indicates threads that are waiting for the GIL
--
Traceback (most recent call last):
  File 
"/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/test/test_gdb.py", 
line 706, in test_threads
self.assertIn('Waiting for the GIL', gdb_output)
AssertionError: 'Waiting for the GIL' not found in 'Breakpoint 1 at 0x9e36a: 
file Python/bltinmodule.c, line 962.\n[Thread debugging using libthread_db 
enabled]\nUsing host libthread_db library 
"/lib/arm-linux-gnueabi/libthread_db.so.1".\n[New Thread 0x2b2b2470 (LWP 
8779)]\n[New Thread 0x2b5ff470 (LWP 8780)]\n[New Thread 0x2b8ff470 (LWP 
8781)]\n[New Thread 0x2baff470 (LWP 8782)]\n\nBreakpoint 1, builtin_id 
(self=, v=42) at Python/bltinmodule.c:962\n962\t   
 return PyLong_FromVoidPtr(v);\n\nThread 5 (Thread 0x2baff470 (LWP 
8782)):\nTraceback (most recent call first):\n  File "", line 10, in 
run\n  File 
"/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/threading.py", 
line 639, in _bootstrap_inner\nself.run()\n  File 
"/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/threading.py", 
line 616, in _bootstrap\nself._bootstrap_inner()\n\nThread 4 (Thread 
0x2b8ff470 (LWP 8781)):\nTraceback (most recent call first):\n  File "", line 10, in run\n  File 
"/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/threading.py", 
line 639, in _bootstrap_inner\nself.run()\n  File 
"/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/threading.py", 
line 616, in _bootstrap\nself._bootstrap_inner()\n\nThread 3 (Thread 
0x2b5ff470 (LWP 8780)):\nTraceback (most recent call first):\n  File 
"", line 10, in run\n  File 
"/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/threading.py", 
line 639, in _bootstrap_inner\nself.run()\n  File 
"/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/threading.py", 
line 616, in _bootstrap\nself._bootstrap_inner()\n\nThread 2 (Thread 
0x2b2b2470 (LWP 8779)):\nTraceback (most recent call first):\n  File 
"", line 10, in run\n  File 
"/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/threading.py", 
line 639, in _bootstrap_inner\nself.run()\n  File 
"/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/thread
 ing.py", line 616, in _bootstrap\nself._bootstrap_inner()\n\nThread 1 
(Thread 0x2aac5300 (LWP 8776)):\nTraceback (most recent call first):\n  File 
"", line 18, in \n'


http://buildbot.python.org/all/builders/ARM%20Ubuntu%203.x

--
stage: patch review -> committed/rejected
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

[issue15449] Optional size argument for readline()

[Sworddragon]

New submission from Sworddragon :

For file objects the read() function has the optional size argument to limit 
the data that will be read. I'm wondering why there isn't such an argument for 
readline(). Theoretically lines in a file could have million of characters and 
even much more. An optional limit could prevent that a high amount of data will 
be load into the memory.

--
components: Library (Lib)
messages: 166422
nosy: Sworddragon
priority: normal
severity: normal
status: open
title: Optional size argument for readline()
type: enhancement
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

[issue15444] Incorrectly written contributor's names

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

All names interpreted correctly except cyrillic (Alexander “Саша” Belopolsky 
and Марк Коренберг). I think it's just because of lack of some non-installed 
package (of course, Latex supports cyrillic).

--

___
Python tracker 

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

[issue15437] Merge Doc/ACKS.txt names into Misc/ACKS

[Éric Araujo]

Éric Araujo  added the comment:

We can just use :source:`Misc/ACKS` and it will created a link to hgweb (the 
colored HTML page, not the raw file).

--

___
Python tracker 

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

[issue15444] Incorrectly written contributor's names

[Ezio Melotti]

Ezio Melotti  added the comment:

> Indeed, PDF rendering is important. OTOH, Latex T1 does support Ž.

I tried to put a Ž directly in an rst source and indeed the pdf has been 
created correctly.

--

___
Python tracker 

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

[issue15269] Document dircmp.left and dircmp.right

[Chris Jerdonek]

Chris Jerdonek  added the comment:

Thanks a lot, Eli, and for the suggestions.  I would be happy to prepare a full 
patch.

Regarding the stream argument, I think there are other changes to dircmp that 
would be more useful (e.g. issue 12932), but I agree that some form of your 
suggestion makes sense.  Would you mind if I created a separate issue for it to 
discuss there?  I have some suggestions on it, and I would be happy to work on 
it there.

--

___
Python tracker 

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

[issue15445] Ability to do code injection via logging module configuration listener port.

[Roundup Robot]

Roundup Robot  added the comment:

New changeset f30b49a5072e by Vinay Sajip in branch '2.7':
Issue #15445: Updated logging configuration documentation to highlight 
potential security risk posed by listen() in certain scenarios.
http://hg.python.org/cpython/rev/f30b49a5072e

New changeset e5d7d202f2bf by Vinay Sajip in branch '3.2':
Issue #15445: Updated logging configuration documentation to highlight 
potential security risk posed by listen() in certain scenarios.
http://hg.python.org/cpython/rev/e5d7d202f2bf

New changeset 410be02de1c6 by Vinay Sajip in branch 'default':
Closes #15445: Merged documentation update from 3.2.
http://hg.python.org/cpython/rev/410be02de1c6

--
nosy: +python-dev
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

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

[issue14930] Make memoryview weakrefable

[Stefan Krah]

Stefan Krah  added the comment:

r75484 should be b595e1ad5722.

--

___
Python tracker 

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

[issue15444] Incorrectly written contributor's names

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Indeed, PDF rendering is important. OTOH, Latex T1 does support Ž. Untested, 
\v{Z} should generate that character. If this doesn't work, the build process 
needs to be fixed.

--

___
Python tracker 

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

[issue15443] datetime module has no support for nanoseconds

[Vincenzo Ampolo]

Vincenzo Ampolo  added the comment:

Have a look to this python dev mailing list thread too:

http://mail.python.org/pipermail/python-dev/2012-July/121123.html

--

___
Python tracker 

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

[issue15448] utimes() functions fail with ENOSYS even when detected by configure

[Richard Moseley]

New submission from Richard Moseley :

When building on a ASUS Eee PC 1000 running the original Xandros O/S with 
libc-2.7-13, the various utimes() functions are being detected as available for 
use, everything compiles. However, during installation of the lib-dynload 
libraries, the error 'Error: Function not implemented' is given and the 
installation halts.

This problem has been tracked down to the fact that some of the utimes() 
functions will return ENOSYS rather than the expected result.

I have now patched the configure.ac script to check for the seven variants of 
the function, which is attached. This patch would ideally have made use of the 
same model as the AC_CHCEK_FUNCS macro but this would require adding a new file 
to the source tree.

--
components: Build
files: configure.ac.diff
keywords: patch
messages: 166413
nosy: richmose
priority: normal
severity: normal
status: open
title: utimes() functions fail with ENOSYS even when detected by configure
type: compile error
versions: Python 3.3
Added file: http://bugs.python.org/file26514/configure.ac.diff

___
Python tracker 

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

[issue14930] Make memoryview weakrefable

[Stefan Krah]

Stefan Krah  added the comment:

Sorry folks, I messed up the revisions when testing. This commit has
nothing to do with the decreased coverage.

Now I properly bisected and in r75481 mbuf_clear() and memory_clear()
are still covered, but in r75484 they are not.

r75484 addresses #1469629. I've got to figure out whether the changed
behavior is expected or not.

--

___
Python tracker 

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

[issue15437] Merge Doc/ACKS.txt names into Misc/ACKS

[Martin v . Löwis]

Martin v. Löwis  added the comment:

I don't think the docs should display Misc/ACKS. Instead, I propose the 
following wording

"Many people have contributed to the Python language, the Python standard 
library, and the Python documentation. See Misc/ACKS in the Python source 
distribution for a partial list of contributors"

It might be useful to link "Misc/ACKS" to 
http://hg.python.org/cpython/file/default/Misc/ACKS
(http://hg.python.org/cpython/raw-file/default/Misc/ACKS would be better if 
hgweb wouldn't declare that application/octet-stream)

--

___
Python tracker 

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

[issue15439] Include Misc/ACKS names into the documentation

[Martin v . Löwis]

Martin v. Löwis  added the comment:

OK, I propose to completely drop the Doc/ACKS.txt from the documentation, and 
replace it with the words

"Many people have contributed to the Python language, the Python standard 
library, and the Python documentation. See Misc/ACKS in the Python source 
distribution for a partial list of contributors"

--

___
Python tracker 

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

[issue15439] Include Misc/ACKS names into the documentation

[Ezio Melotti]

Ezio Melotti  added the comment:

FWIW including Misc/ACKS in the doc will probably break the generation of the 
pdf version of the doc, since it contains non-latin1 characters (see 
msg166408).  I don't think it's necessary to include the names in the doc.

> I don't know how Doc ACKS is maintained, but I think the devguide is
> fine as it stands, whether or not Doc ACKS is preserved or not. 
> People should put themselves into Misc/ACKS if they made a 
> contribution, period.

In my experience Doc/ACKS.txt is mostly ignored/unmaintained.  I did a lot of 
work on the docs and my name is not in there, and I don't think I ever added 
anyone there.

> If people need to be acknowledged separately for contributing to the
> documentation, I think only major contributions (such as writing the 
> documentation for a yet-undocumented module) should be explicitly 
> acknowledged.

It's already possible to give credit directly in the docs using directives like 
"sectionauthor".

--

___
Python tracker 

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

[issue15444] Incorrectly written contributor's names

[Ezio Melotti]

Ezio Melotti  added the comment:

Make sure that it's still possible to generate the pdf of the docs (with `make 
latex` and then `make all-pdf` in build/latex/).
Latin1 should be fine, but IIRC non-latin1 will break (sorry Žiga).

--
nosy: +ezio.melotti

___
Python tracker 

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

[issue15444] Incorrectly written contributor's names

[Chris Jerdonek]

Chris Jerdonek  added the comment:

To be clear on this issue's scope, I would state in a single comment a white 
list of which directories or individual files are being corrected (or if 
necessary, the rules to determine such a list, e.g. any file whose name root is 
"NEWS", etc).

I would also recommend being systematic about this by creating a script to 
search the above files, along with a configuration section containing the list 
of replacements: e.g. correct spelling -> list of misspellings for that name.  
And upload the script to this issue.  That way people can see what misspellings 
have already been accounted for, more could be added easily, and it could be 
used again if necessary.

Because this may grow in scope (e.g. into source files) and because it affects 
people's names, it may be worth raising on python-dev.  At the least, people 
would have the chance to contribute known misspellings.

--

___
Python tracker 

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

[issue14930] Make memoryview weakrefable

[Richard Oudkerk]

Richard Oudkerk  added the comment:

Is it possible that the use of test.support.gc_collect() in test_memoryview 
made the difference?

--

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Meador Inge]

Meador Inge  added the comment:

While looking this up in the C Standard (ISO/IEC 9899:TC3) I also noticed 
6.3.2.3p8:

"""
A pointer to a function of one type may be converted to a pointer to a function 
of another
type and back again; the result shall compare equal to the original pointer. If 
a converted
pointer is used to call a function whose type is not compatible with the 
pointed-to type, the behavior is undefined.
"""

I will add the 'unused' parameter back with my refresh patch.

--

___
Python tracker 

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

[issue15447] A file is not properly closed by webbrowser._invoke

[R. David Murray]

R. David Murray  added the comment:

You could do it either way.  Normally we prefer to have a test along with any 
fix; in this case adding a test involves adding the test module as well, but it 
is not different in principle.  If you want to work on it and prefer to have it 
as a separate issue that's fine, we'll just make the test issue dependent on 
this one.

--

___
Python tracker 

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

[issue15438] Incredible issue in math.pow

[Mark Dickinson]

Mark Dickinson  added the comment:

> Wouldn't that reinforce the misconception that math is for arbitrary
> precision number theoretical functions?

Perhaps.  We already have math.factorial, though;  adding math.powmod wouldn't 
seem so much of a stretch.  Just to be clear, I'm not seriously proposing this 
for any version of Python before 4.0; apologies for derailing the issue thread.

--

___
Python tracker 

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

[issue15438] Incredible issue in math.pow

[Stefan Krah]

Stefan Krah  added the comment:

Ramchandra Apte  wrote:
> > [+1 for removing pow from the builtins and shunting three-argument pow to 
> > the math module in Python 500.]
> Anybody who uses pow with three is doing something mathematical and has most 
> likely imported math already.

Wouldn't that reinforce the misconception that math is for arbitrary precision
number theoretical functions? The OP used it for cryptography.

--

___
Python tracker 

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

[issue15447] A file is not properly closed by webbrowser._invoke

[Anton Barkovsky]

Anton Barkovsky  added the comment:

Adding a patch that uses subprocess.DEVNULL instead.

Writing tests for webbrowser should be a separate issue, right?

--
Added file: http://bugs.python.org/file26513/fileclose_devnull.patch

___
Python tracker 

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

[issue12834] PyBuffer_ToContiguous() incorrect for non-contiguous arrays

[Stefan Krah]

Stefan Krah  added the comment:

Here's a patch for 3.3, which consists mostly of tests. A couple of points:

  o I removed the len > view->len check in PyBuffer_ToContiguous(), since
the function is not documented and silently accepting output buffers
that are too large seems unusual to me.

  o Removed the comment in bytesobject.c "Better way to get to internal 
buffer?".
IMO the answer is no: There isn't any better way that works in full 
generality.

  o Removed the "need to check for overflow" comment: ndim is now officially
limited to 64.


I think this can go into 3.3: It's easy to see that for contiguous buffers
PyBuffer_ToContiguous() behaves in the same manner as before (except for
the len issue).

For memoryview, buffer_to_contiguous(x, y 'C') is literally the same
code as buffer_to_c_contiguous().

--
keywords: +patch
Added file: http://bugs.python.org/file26512/issue12834.diff

___
Python tracker 

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

[issue15447] A file is not properly closed by webbrowser._invoke

[R. David Murray]

R. David Murray  added the comment:

@Anton: That's what I was guessing.  If we had a unit test in test_webbrowser 
that did the same thing, we'd have seen the resource warning when running the 
tests and fixed it.  However, it looks like there aren't *any* tests for 
webbrowser, not even in test_sundry (which just makes sure modules without 
tests are importable).

So adding a test that will trigger this resource warning requires setting up a 
test_webbrowser file first, even before we get to the problem of how to test 
something that wants to start up a web browser...(but that should be solvable 
with unittest.mock, I think).

--

___
Python tracker 

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

[issue15438] Incredible issue in math.pow

[Ramchandra Apte]

Ramchandra Apte  added the comment:

> [+1 for removing pow from the builtins and shunting three-argument pow to the 
> math module in Python 500.]
Me too.
Anybody who uses pow with to arguments can use arg1**arg2
Anybody who uses pow with three is doing something mathematical and has most 
likely imported math already.

--
nosy: +ramchandra.apte

___
Python tracker 

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

[issue15447] A file is not properly closed by webbrowser._invoke

[Ross Lagerwall]

Ross Lagerwall  added the comment:

Are there any webbrowser unit tests?

(this could probably use the new subprocess.DEVNULL constant in 3.3)

--
nosy: +rosslagerwall

___
Python tracker 

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

[issue15447] A file is not properly closed by webbrowser._invoke

[Anton Barkovsky]

Anton Barkovsky  added the comment:

To clarify, I discovered this when I was simply running webbrowser.open
in REPL.

--

___
Python tracker 

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

[issue15447] A file is not properly closed by webbrowser._invoke

[Anton Barkovsky]

Anton Barkovsky  added the comment:

The warning is printed by the file object when it closes itself in __del__:

  ResourceWarning: unclosed file <_io.TextIOWrapper name='/dev/null' mode='r+' 
encoding='UTF-8'>

There isn't much to test, or is there?

--

___
Python tracker 

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

[issue15447] A file is not properly closed by webbrowser._invoke

[R. David Murray]

R. David Murray  added the comment:

Thanks.  Is this warning printed by the webbrowser unit tests?  If not can you 
see a way to add one that does?

--
nosy: +r.david.murray

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Stefan: not sure whether raising this to python-dev really helps; see also  
msg42177, msg58196, issue1648268, and msg75239. Feel free to raise it, though.

--

___
Python tracker 

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

[issue15447] A file is not properly closed by webbrowser._invoke

[Anton Barkovsky]

New submission from Anton Barkovsky :

webbrowser._invoke opens /dev/null, never closes it and a warning is
printed.

I'm attaching a patch.
The diff looks messy, but I'm just wrapping the code in a try-finally
block, the rest is just indented.

--
components: Library (Lib)
files: fileclose.patch
keywords: patch
messages: 166392
nosy: anton.barkovsky
priority: normal
severity: normal
status: open
title: A file is not properly closed by webbrowser._invoke
type: behavior
versions: Python 3.4
Added file: http://bugs.python.org/file26511/fileclose.patch

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Martin v . Löwis]

Martin v. Löwis  added the comment:

Jesús: this is a (common) mistake. Standard C makes it undefined behavior to 
call a function with an incorrect number of arguments, see 6.5.2.2p9

# If the function is defined with a type that is not compatible with the 
# type (of the expression) pointed to by the expression that denotes the 
# called function, the behavior is undefined.

Two function pointers are compatible if the function types are compatible 
(6.7.5.1p2), which in turn is defined in 6.7.5.3p15,
which is too long to quote here.

Your understanding of the parameter passing convention is not part of the 
language definition. The only way to have more parameters in the call than are 
declared is by means of an ellipsis. 

There is an exception for "old style" (K&R) functions and declarations, but it 
doesn't apply here.

--

___
Python tracker 

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

[issue15275] isinstance is called a more times that needed in ntpath

[Ezio Melotti]

Ezio Melotti  added the comment:

> I don't know about a decent way of doing benchmarks for the changes.
> Any recommendation?

You could make a script that uses the timeit module.

>> If this patch is applied I think it would be good to change
>> posixpath too.
> I agree and I'd love to do it but in a diff bug to make things
> self-contained, what do you think?

Having a single patch that fixes both is OK.

--

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Jesús Cea Avión]

Jesús Cea Avión  added the comment:

I think that C standard actually documents the parameter order placement, so 
you can left out the last ones in the actual function definition.

So, that this is working is not an accident, it is a C standard requirement.

I think...

--

___
Python tracker 

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

[issue15424] __sizeof__ of array should include size of items

[Ludwig Hähne]

Ludwig Hähne  added the comment:

Revised the patch based on the discussion in issue #15402 
(http://bugs.python.org/msg166372). It doesn't typecast the function anymore 
and instead casts to the array type inside the function.

--
Added file: http://bugs.python.org/file26510/array_sizeof_v3.patch

___
Python tracker 

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

[issue15443] datetime module has no support for nanoseconds

[Marc-Andre Lemburg]

Marc-Andre Lemburg  added the comment:

[Roundup's email interface again...]

 x = 86400.0
 x == x + 1e-9
> False
 x == x + 1e-10
> False
 x == x + 1e-11
> False
 x == x + 1e-12
> True

--

___
Python tracker 

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

[issue15443] datetime module has no support for nanoseconds

[Marc-Andre Lemburg]

Marc-Andre Lemburg  added the comment:

Alexander Belopolsky wrote:
> 
> Alexander Belopolsky  added the comment:
> 
> On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg  
> wrote:
>> ... full C double precision for the time part of a timestamp,
>> which covers nanoseconds just fine.
> 
> No, it does not:
> 
 import time
 t = time.time()
 t + 5e-9 == t
> True
> 
> In fact, C double precision is barely enough to cover microseconds:
> 
 t + 1e-6 == t
> False
> 
 t + 1e-7 == t
> True

I was referring to the use of a C double to store the time part
in mxDateTime. mxDateTime uses the C double to store the number of
seconds since midnight, so you don't run into the Unix ticks value
range problem you showcased above.

--

___
Python tracker 

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

[issue15446] Eval Recursion SIGSEGV

[R. David Murray]

Changes by R. David Murray :


--
resolution:  -> duplicate
stage:  -> committed/rejected
status: open -> closed
superseder:  -> stack overflow evaluating eval("()" * 3)
title: Recursion SIGSEGV -> Eval Recursion SIGSEGV

___
Python tracker 

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

[issue15443] datetime module has no support for nanoseconds

[Marc-Andre Lemburg]

Marc-Andre Lemburg  added the comment:

Marc-Andre Lemburg wrote:
> 
>> Alexander Belopolsky  added the comment:
>>
>> On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg  
>> wrote:
>>> ... full C double precision for the time part of a timestamp,
>>> which covers nanoseconds just fine.
>>
>> No, it does not:
>>
> import time
> t = time.time()
> t + 5e-9 == t
>> True
>>
>> In fact, C double precision is barely enough to cover microseconds:
>>
> t + 1e-6 == t
>> False
>>
> t + 1e-7 == t
>> True
> 
> I was referring to the use of a C double to store the time part
> in mxDateTime. mxDateTime uses the C double to store the number of
> seconds since midnight, so you don't run into the Unix ticks value
> range problem you showcased above.

There's enough room to even store 1/100th of a nanosecond, which may
be needed for some physics experiments :-)

False
>>> x == x + 1e-10
False
>>> x == x + 1e-11
False
>>> x == x + 1e-12
True

--

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Stefan Krah]

Stefan Krah  added the comment:

""Everywhere" is nowhere close to the truth. There are tons of
NOARGS functions which have the correct signature."

When I started writing C-extensions, I used the PyObject *unused
idiom. Then I saw Meador's version in so many places in the source
tree that I assumed it's correct.

I think raising this issue on python-dev would be beneficial.

--
nosy: +skrah

___
Python tracker 

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

[issue15443] datetime module has no support for nanoseconds

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

On Wed, Jul 25, 2012 at 4:17 AM, Marc-Andre Lemburg  
wrote:
> ... full C double precision for the time part of a timestamp,
> which covers nanoseconds just fine.

No, it does not:

>>> import time
>>> t = time.time()
>>> t + 5e-9 == t
True

In fact, C double precision is barely enough to cover microseconds:

>>> t + 1e-6 == t
False

>>> t + 1e-7 == t
True

--

___
Python tracker 

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

[issue15445] Ability to do code injection via logging module configuration listener port.

[Vinay Sajip]

Vinay Sajip  added the comment:

I think it is sufficient for 2.7, 3.2 and 3.3 to just update the documentation, 
as Graham says, using "note" markup so that it stands out.

I can look at ast.literal_eval as an option for 3.4.

--

___
Python tracker 

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

[issue14930] Make memoryview weakrefable

[Stefan Krah]

Stefan Krah  added the comment:

A quick question: Prior to this patch test_memoryview.py exercised
both mbuf_clear() and memory_clear(). Now gcov shows no coverage.

Is this expected? Is it still possible to construct tests that
exercise the code?

--

___
Python tracker 

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

[issue15402] Correct __sizeof__ support for struct

[Mark Dickinson]

Mark Dickinson  added the comment:

> The compiler has no chance to find out. You cast the pointer to
> PyCFunction, telling the compiler that it really is a PyCFunction.

True; I was thinking that the compiler should have the necessary information to 
warn about the suspicious (PyCFunction) cast.  But then again the function 
pointer cast is perfectly legal---it's the subsequent call that invokes 
undefined behaviour, and that's in a different file, so the compiler can't help.

> "Everywhere" is nowhere close to the truth.

Yep, sorry;  bad wording on my part.  I didn't intend to imply that all uses of 
METH_NOARGS had this problem.  'Everywhere' for very small values of 
'everywhere'. :-)

--

___
Python tracker 

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

[issue15363] Idle/tkinter ~x.py 'save as' fails. closes idle

[Martin v . Löwis]

Martin v. Löwis  added the comment:

I think this should apply to all systems, and I think the proper escaping is 
with "./", see TclpNativeSplitPath (in Tcl's source code).

--
nosy: +loewis

___
Python tracker 

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

[issue15446] Recursion SIGSEGV

[Arseniy]

New submission from Arseniy :

a=lambda:a
print eval("a" + "()" * 99)

--
components: None
messages: 166378
nosy: senyai
priority: normal
severity: normal
status: open
title: Recursion SIGSEGV
type: crash
versions: Python 2.7, Python 3.3

___
Python tracker 

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