[issue12075] python3.2 memory leak when reloading class with attributes

[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

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

[Nick Coghlan]

New submission from Nick Coghlan:

logging.shutdown includes a try/except block to avoid emitting spurious IO 
errors while the interpreter is shutting down. This fails if a registered 
handler tries to do IO (such as calling flush()) in its release method.

It would be better if the flush-and-close block was written as:

  try:
  hr.acquire()
  try:
  hr.flush()
  hr.close()
  finally:
  hr.release()
  except (IOError, ValueError):
# Tolerate handlers that try to do IO in release()

--
messages: 170635
nosy: ncoghlan
priority: normal
severity: normal
status: open
title: logging.shutdown should cope with IO errors from handler.release methods
versions: Python 2.7, Python 3.2, Python 3.3

___
Python tracker 

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

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

[Nick Coghlan]

Changes by Nick Coghlan :


--
nosy: +vinay.sajip
type:  -> behavior

___
Python tracker 

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

[issue15956] backreference to named group does not work

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc added the comment:

> And why isn't \g part of the pattern language, anyway, or at
> least some way to refer to a match made in a previous *named* group?

But this way exists: (?P=startquote) is what you want.  To me \g is an 
exception, and frankly I did not know about it before this bug report.


I agree that the following sentence could be better structured:
"""
For example, if the pattern is (?P[a-zA-Z_]\w*), the group can be 
referenced by its name in arguments to methods of match objects, such as 
m.group('id') or m.end('id'), and also by name in the regular expression itself 
(using (?P=id)) and replacement text given to .sub() (using \g).
"""

It probably needs to be split into several pieces, contributions are welcome.

--

___
Python tracker 

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

[issue8786] Add support for IEEE 754 contexts to decimal module.

[Michele Orrù]

Michele Orrù added the comment:

Something like this? That's a pretty trivial draft for the patch.

About "byte sequences", those features should be available using builtins 
bin(), oct() and hex(), hacking on __index__, or with internal methods?

I am lacking imagination, what else there should be to test?

--
keywords: +patch
nosy: +ezio.melotti, maker
Added file: http://bugs.python.org/file27214/issue8786.patch

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Stefan Krah]

Stefan Krah added the comment:

So the problem is that readinto(view) might result in several references
to view? I don't think that can be solved on the memoryview side.

One could do:

   view = PyMemoryView_FromObject(b);
   // Lie about writability
   ((PyMemoryViewObject *)view)->view.readonly = 0;

   [...]

Then the view owns a reference to the bytes object. But that does not
solve the problem that writable memoryviews based on a readonly object
might be hanging around.

--

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Richard Oudkerk]

Richard Oudkerk added the comment:

> Then the view owns a reference to the bytes object. But that does not
> solve the problem that writable memoryviews based on a readonly object
> might be hanging around.

How about doing

PyObject_GetBuffer(b, &buf, PyBUF_WRITABLE);
view = PyMemoryView_FromBuffer(&buf);
// readinto view
PyBuffer_Release(&buf);

Would attempts to access a "leaked" reference to view now result in 
ValueError("operation forbidden on released memoryview object")?  If so then I 
think this would be safe.

--

___
Python tracker 

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

[issue15961] Missing return value in ``system_message``

[Malthe Borch]

New submission from Malthe Borch:

When ``docutils`` are importable, distutils uses a reporter implementation that 
incorrectly drops a return value from the ``system_message`` override (see 
patch).

--
assignee: eric.araujo
components: Distutils
files: patch.diff
keywords: patch
messages: 170640
nosy: eric.araujo, malthe, tarek
priority: normal
severity: normal
status: open
title: Missing return value in ``system_message``
type: behavior
versions: Python 2.7, Python 3.2
Added file: http://bugs.python.org/file27215/patch.diff

___
Python tracker 

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

[issue15962] Windows STDIN/STDOUT Redirection is actually FIXED

[Nacsa Kristóf]

New submission from Nacsa Kristóf:

The Python docs faq says that due to a bug in Windows NT's cmd.exe, the output 
redirection and piping won't work when started from file extension.

http://docs.python.org/faq/windows.html#how-do-i-make-python-scripts-executable
http://docs.python.org/py3k/faq/windows.html#how-do-i-make-python-scripts-executable

This is actually fixed in Windows, but the fix is disabled by default, and you 
need to enable it in regedit, the keyword is "InheritConsoleHandles".

Proof & Details:
http://support.microsoft.com/default.aspx?kbid=321788

It would be great if the docs could refer to this fix, as the docs is the major 
source of information for many.

--
assignee: docs@python
components: Documentation, Installation, Windows
messages: 170641
nosy: Nacsa.Kristóf, docs@python
priority: normal
severity: normal
status: open
title: Windows STDIN/STDOUT Redirection is actually FIXED
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4

___
Python tracker 

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

[issue15962] Windows STDIN/STDOUT Redirection is actually FIXED

[Ezio Melotti]

Changes by Ezio Melotti :


--
keywords: +easy
nosy: +brian.curtin, terry.reedy, tim.golden
stage:  -> needs patch
type:  -> enhancement
versions:  -Python 2.6, Python 3.1

___
Python tracker 

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

[issue8425] a -= b should be fast if a is a small set and b is a large set

[Michele Orrù]

Changes by Michele Orrù :


--
nosy: +maker

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Richard Oudkerk]

Richard Oudkerk added the comment:

The current non-test uses of PyMemoryView_FromBuffer() are in 
_io.BufferedReader.read(), _io.BufferedWriter.write(), PyUnicode_Decode().

It looks like they can each be made to leak a memoryview that references a 
deallocated buffer.  (Maybe the answer is Don't Do That.)


import codecs, sys

def decode(buf):
global view
view = buf
return codecs.latin_1_decode(buf)

def getregentry():
return codecs.CodecInfo(name='foobar', decode=decode,
encode=codecs.latin_1_encode)

@codecs.register
def search_function(encoding):
if encoding == 'foobar':
return codecs.CodecInfo(*getregentry())

b = b'hello'.upper()
b.decode('foobar')
print(view.tobytes())   # => b'HELLO'
del b
x = b'dump'.upper()
print(view.tobytes())   # => b'DUMP\x00'



import io, sys

class File(io.RawIOBase):
def readinto(self, buf):
global view
view = buf
n = len(buf)
buf[:] = b'x'*n
return n

def readable(self):
return True

f = io.BufferedReader(File())
f.read(1)
print(view[:5].tobytes())   # => b'x'
del f
print(view[:5].tobytes())   # => b'\xdd\xdd\xdd\xdd\xdd'

--

___
Python tracker 

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

[issue15745] Numerous utime ns tests fail on FreeBSD w/ ZFS (update: and NetBSD w/ FFS, Solaris w/ UFS)

[Trent Nelson]

Changes by Trent Nelson :


--
title: Numerous utime ns tests fail on FreeBSD w/ ZFS -> Numerous utime ns 
tests fail on FreeBSD w/ ZFS (update: and NetBSD w/ FFS, Solaris w/ UFS)

___
Python tracker 

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

[issue9720] zipfile writes incorrect local file header for large files in zip64

[Kristof Keppens]

Changes by Kristof Keppens :


--
nosy: +Kristof.Keppens

___
Python tracker 

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

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

[Trent Nelson]

New submission from Trent Nelson:

Gripe: if you want a 64-bit, non-gcc (i.e. vendor's cc) build on a proprietary 
UNIX system (i.e. Solaris, HP-UX, AIX etc), "you're going to have a bad time".

Coercing a 64-bit build from a vendor's cc currently requires explicit 
CFLAGS/LDFLAGS/configure gymnastics for each platform.  It's a pain.

Initial goal: use this issue to document the gymnastics.

Assumption: once all the different techniques are documented, it'll be easier 
to assess what changes would be appropriate to configure.in.

Side bar design question: on BSD/Linux/OSX w/ gcc/clang, if you're on an amd64 
platform, you'll get a 64-bit build.  This isn't the case for Solaris, HP-UX 
and AIX -- the default is always 32-bit.  You need aforementioned gymnastics to 
coerce a 64-bit build.

Is this by design?  If so, then I guess I'm proposing that ./configure should 
have a `--with-64`-type argument that'll generate a 64-bit build.

If not, then we need to decide whether to change the default behavior such that 
./configure always generates a 64-bit build if you're on a 64-bit platform -- 
if you want a 32-bit build, you need to explicitly tell ./configure (i.e. 
--with-32).

Changing the default is probably only viable for 3.4 onwards.  It'd be nice if 
2.7->3.3 had generic configure support for 64-bit builds though (via --with-64).

XXX TODO for trent: review autoconf's offerings... getting 64-bit builds from 
vendor cc's can't be that unusual.

--
assignee: trent
components: Build
messages: 170643
nosy: trent
priority: low
severity: normal
status: open
title: Improve ./configure's support for 32/64-bit debug|release|profiled 
builds w/ vendor (non-gcc) compilers on proprietary UNIX systems 
(Solaris/HP-UX/AIX et al).
type: enhancement
versions: Python 2.7, Python 3.4

___
Python tracker 

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

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

[Trent Nelson]

Trent Nelson added the comment:

On the s10 slave (Solaris 10/nitrogen) for 3.x:

(cpython@nitrogen:ttypts/4) (Tue/12:32) ..  

   
% ../../src/configure --with-pydebug --without-gcc CFLAGS="-m64 -mt 
-xcheck=%all -g3 -xarch=native -xchip=native" CPPFLAGS="-IInclude" OPT="" 
LDFLAGS="-m64 -mt -xcheck=%all -g3 -xarch=native -xchip=native" 
CC=/opt/solarisstudio12.3/bin/cc

--

___
Python tracker 

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

[issue9720] zipfile writes incorrect local file header for large files in zip64

[Christian Heimes]

Christian Heimes added the comment:

Serhiy:
If I understand you correctly it should be easy to fix. The code in close() has 
to check if any file is beyond the ZIP64 limit and then write all headers with 
extra args. Is that correct?

--
keywords: +needs review
nosy: +christian.heimes

___
Python tracker 

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

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

[Jeremy Kloth]

Changes by Jeremy Kloth :


--
nosy: +jkloth

___
Python tracker 

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

[issue15964] SyntaxError in asdl when building 2.7 with system Python 3

[Chris Jerdonek]

New submission from Chris Jerdonek:

Building with--

./configure --with-pydebug && make -j2

errors out after switching branches from default to 2.7 when the system Python 
is Python 3 (on Mac OS X 10.7.4 using MacPorts).

To reproduce:

$ sudo port select python python32
$ python
No such file or directory
$ python3 -V
Python 3.2.3
$ hg update default
$ ./configure --with-pydebug && make -j2
$ hg update 2.7
$ cp Modules/Setup.dist Modules/Setup
$ ./configure --with-pydebug && make -j2
...
config.status: creating pyconfig.h
config.status: pyconfig.h is unchanged
creating Modules/Setup
creating Modules/Setup.local
creating Makefile
./install-sh -c -d Include
./Parser/asdl_c.py -h Include ./Parser/Python.asdl
gcc -c -fno-strict-aliasing -g -O2 -g -O0 -Wall -Wstrict-prototypes  -I. 
-IInclude -I./Include   -DPy_BUILD_CORE -o Parser/printgrammar.o 
Parser/printgrammar.c
gcc -c -fno-strict-aliasing -g -O2 -g -O0 -Wall -Wstrict-prototypes  -I. 
-IInclude -I./Include   -DPy_BUILD_CORE -o Parser/pgenmain.o Parser/pgenmain.c
  File "./Parser/asdl_c.py", line 1
print "Must specify exactly one output file"
   ^
SyntaxError: invalid syntax
make: *** [Include/Python-ast.h] Error 1
make: *** Waiting for unfinished jobs

Running "make distclean" doesn't fix this.  Here is one work-around:

$ sudo port select python python27
$ ./configure --with-pydebug && make -j2

Perhaps the right work-around can be documented in the devguide, or maybe this 
can be addressed another way.

--
components: Build
messages: 170646
nosy: cjerdonek
priority: normal
severity: normal
status: open
title: SyntaxError in asdl when building 2.7 with system Python 3
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

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

[Vinay Sajip]

Vinay Sajip added the comment:

I'm not against making this change, but I'm curious - why would a handler do 
clean-up I/O in its release() method (which is just for releasing the I/O lock) 
where it could just as easily override the close() method to do the same thing? 
It seems like programmer error to be doing any I/O in a handler after close() 
is called on it.

--

___
Python tracker 

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

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

[Trent Nelson]

New submission from Trent Nelson:

On Solaris (s10/nitrogen):


% find /usr/include -type f | xargs fgrep -ni AT_FDCWD
/usr/include/sys/fcntl.h:320:#defineAT_FDCWD
0xffd19553

(AIX uses -2, FreeBSD uses -100.)

Anyway, that results in:


(cpython@nitrogen:ttypts/10) (Tue/15:34) .. 

(~/hg/3.x.trent/build/release)
% touch ../../src/Modules/posixmodule.c 
(cpython@nitrogen:ttypts/10) (Tue/15:34) .. 

(~/hg/3.x.trent/build/release)
% time /usr/ccs/bin/make 
/opt/solarisstudio12.3/bin/cc  -DNDEBUG -v -m64 -mt=yes -xbuiltin -xhwcprof -xF 
-xarch=native -xchip=native -fast -fma=fused -g -xO4 -library=sunperf   -I. 
-I../../src/Include -IInclude   -DPy_BUILD_CORE  -c 
../../src/Modules/posixmodule.c -o Modules/posixmodule.o
"../../src/Modules/posixmodule.c", line 2307: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 2337: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 2386: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 2626: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 2966: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 3198: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 3199: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 3845: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 3989: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 3990: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 4111: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 4267: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 4587: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 7007: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 7092: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 7510: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 8260: warning: initializer does not fit 
or is out of range: 0xffd19553
"../../src/Modules/posixmodule.c", line 8322: warning: initializer does not fit 
or is out of range: 0xffd19553
^C
*** Modules/posixmodule.o removed.
/usr/ccs/bin/make  2.79s user 0.28s system 46% cpu 6.598 total

In every case, the affected line is:

int dir_fd = DEFAULT_DIR_FD;

(DEFAULT_DIR_FD defaults to AT_FDCWD if it's defined.)

Note that Solaris 10 64-bit is LP64, ints are still 32-bit.

--
assignee: trent
components: Build
messages: 170648
nosy: trent
priority: normal
severity: normal
stage: needs patch
status: open
title: AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.
type: compile error

___
Python tracker 

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

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

[R. David Murray]

Changes by R. David Murray :


--
nosy: +larry

___
Python tracker 

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

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

[Trent Nelson]

Trent Nelson added the comment:

Easy fix, cast AT_FDCWD to (int):


% hg diff
diff -r 3a880d640981 Modules/posixmodule.c
--- a/Modules/posixmodule.c Tue Sep 18 07:21:18 2012 +0300
+++ b/Modules/posixmodule.c Tue Sep 18 16:04:58 2012 +
@@ -414,7 +414,14 @@
 
 
 #ifdef AT_FDCWD
-#define DEFAULT_DIR_FD AT_FDCWD
+/*
+ * Why the (int) cast?  Solaris 10 defines AT_FDCWD as 0xffd19553 (-3041965);
+ * without the int cast, the value gets interpreted as uint (4291925331),
+ * which doesn't play nicely with all the initializer lines in this file that
+ * look like this:
+ *  int dir_fd = DEFAULT_DIR_FD;
+ */
+#define DEFAULT_DIR_FD (int)AT_FDCWD
 #else
 #define DEFAULT_DIR_FD (-100)
 #endif


The cast is harmless on other platforms that use an actual integer (rather than 
a hex representation).

Any objections?

--

___
Python tracker 

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

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

[Mark Dickinson]

New submission from Mark Dickinson:

The submit methods of concurrent.futures.ThreadPoolExecutor and 
concurrent.futures.ProcessPoolExectutor raise TypeError when submitting a 
callable with a keyword argument named 'fn' or 'self':

Python 3.3.0rc2+ (default:3a880d640981, Sep 18 2012, 16:29:28) 
[GCC 4.2.1 (Apple Inc. build 5664)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import concurrent.futures
>>> def awkward(*, fn): return fn * 1729
... 
>>> with concurrent.futures.ThreadPoolExecutor(1) as e:
... e.submit(awkward, fn=3)
... 
Traceback (most recent call last):
  File "", line 2, in 
TypeError: submit() got multiple values for argument 'fn'


An obvious solution is to change the declarations of the submit methods from:

def submit(self, fn, *args, **kwargs):
...

to

def submit(*args, **kwargs):
self, fn, *args = args


I don't think this is quite good enough, since it'll introduce a regression for 
anyone who was doing executor.submit(fn=...).

--
messages: 170650
nosy: mark.dickinson
priority: normal
severity: normal
status: open
title: concurrent.futures: Executor.submit keyword arguments may not be called 
'fn' (or 'self')
type: behavior
versions: Python 3.2, Python 3.3

___
Python tracker 

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

[issue2286] Stack overflow exception caused by test_marshal on Windows x64

[Trent Nelson]

Trent Nelson added the comment:

Closing issue; this has been 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

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

[Mark Dickinson]

Mark Dickinson added the comment:

Here's a patch.  The solution is ugly enough that I'm wondering whether this is 
even worth fixing.

--
keywords: +patch
Added file: http://bugs.python.org/file27216/futures.patch

___
Python tracker 

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

[issue15955] gzip, bz2, lzma: add method to get decompressed size

[Éric Araujo]

Changes by Éric Araujo :


--
nosy: +eric.araujo

___
Python tracker 

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

[issue15957] README.txt points to broken "contributing" url in python wiki

[Éric Araujo]

Éric Araujo added the comment:

Thanks for the report.   I think the wiki was modified to redirect /thing to 
/moin/thing some months ago, so it may be the recent hardware migration that 
broke that.  I’ll follow up with the pydotorg-www mailing list (or feel free to 
do it).

--
assignee: docs@python -> eric.araujo
nosy: +eric.araujo -docs@python

___
Python tracker 

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

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

[Éric Araujo]

Changes by Éric Araujo :


--
nosy: +eric.araujo, loewis
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

[issue15961] Missing return value in ``system_message``

[Éric Araujo]

Éric Araujo added the comment:

Thanks for the report and patch.  I think a similar issue was reported for 
distutils2 (maybe only orally, not on this tracker, I have to search).  How did 
you find the bug?  In other words, can you add a unit test for this? :)

--
components: +Distutils2
nosy: +alexis
stage:  -> test needed
versions: +3rd party, Python 3.3

___
Python tracker 

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

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

[Michael Foord]

Michael Foord added the comment:

The patch is just waiting for me to look over it and commit. I'll get to it 
ASAP.

--

___
Python tracker 

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

[issue4711] Wide literals in the table of contents overflow in documentation

[Éric Araujo]

Changes by Éric Araujo :


--
nosy: +eric.araujo

___
Python tracker 

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

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

[Vitaly]

Vitaly added the comment:

In the work-around, we need to watch out for what 'man 2 read' on Mac OS refers 
to as "normal file":

==
Upon successful completion, read(), readv(), and pread() return the number of 
bytes actually read and placed in the buffer.  *The system  guarantees to 
read the number of bytes requested if the descriptor references a normal file 
that has that many bytes left before the end-of-file*, but in no other case.
==

I am guessing that fstat() + S_ISREG() can be used to discern "normal files" 
from other types of file descriptors.

--

___
Python tracker 

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

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

[Ralf Schmitt]

Changes by Ralf Schmitt :


--
nosy: +schmir

___
Python tracker 

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

[issue15956] backreference to named group does not work

[Matthew Barnett]

Matthew Barnett added the comment:

There needed to be a way of referring to named groups in the replacement 
template. The existing form \groupnumber clearly wouldn't work. Other regex 
implementations, such as Perl, do have \g and also \k (for named groups).

In my implementation I added support for \g in regex strings.

--

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Richard Oudkerk]

Richard Oudkerk added the comment:

I am rather confused about the ownership semantics when one uses 
PyMemoryView_FromBuffer().

It looks as though PyMemoryView_FromBuffer() "steals" ownership of the buffer 
since, when the associated _PyManagedBufferObject is garbage collected, 
PyBuffer_Release() is called on its copy of the buffer info.  However, the 
_PyManagedBufferObject does not own a reference of the base object, so one 
still needs to decref the base object (at some time when it is safe to do so).

So am I right in thinking that

  PyObject_GetBuffer(obj, &buf, ...);
  view = PyMemoryView_FromBuffer(&buf); // view->master owns the buffer, 
but view->master->obj == NULL
  ...
  Py_DECREF(view);  // releases buffer (assuming no 
other exports)
  Py_XDECREF(buf.obj);

has balanced refcounting and is more or less equivalent to

  view = PyMemoryView_FromObject(obj);
  ...
  Py_DECREF(view);

The documentation is not very helpful.  It just says that calls to 
PyObject_GetBuffer() must be matched with calls to PyBuffer_Release().

--

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Stefan Krah]

Stefan Krah added the comment:

Richard Oudkerk  wrote:
> PyObject_GetBuffer(b, &buf, PyBUF_WRITABLE);
> view = PyMemoryView_FromBuffer(&buf);
> // readinto view
> PyBuffer_Release(&buf);
> 
> Would attempts to access a "leaked" reference to view now result in 
> ValueError("operation forbidden on released memoryview object")?  If so then 
> I think this would be safe.

You would need to call memory_release(). Perhaps we can just expose it on the
C-API level as PyMemoryView_Release().

IMO the use of PyObject_GetBuffer() should be discouraged. The semantics
aren't clear (see #15821). I'd suggest using:

  1) A buffer provider is involved (the case here):

PyMemoryView_From Object()

  2) A piece of memory needs to be wrapped temporarily and no references
 to the memoryview are "leaked" on the Python level:

PyMemoryView_FromMemory()

  3) A piece of memory needs to be packaged as a memoryview with automatic
 cleanup in mbuf_dealloc():

PyMemoryView_FromBufferWithCleanup() (proposed in msg169613)

So I think the combination of PyMemoryView_FromObject() with a call to
PyMemoryView_Release() should indeed work here.

--

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Stefan Krah]

Stefan Krah added the comment:

Richard Oudkerk  wrote:
> The documentation is not very helpful.  It just says that calls
> to PyObject_GetBuffer() must be matched with calls to PyBuffer_Release().

Yes, we need to sort that out, see #15821.

--

___
Python tracker 

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

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

[Trent Nelson]

Trent Nelson added the comment:

Solaris 10 release (i.e. optimized) build requires the following:

../../src/configure --without-gcc CFLAGS="-v -fsimple=0 -m64 -mt=yes -xbuiltin 
-xhwcprof -xF -xarch=native -xchip=native -fma=fused -g -xO5 -xlibmil -xlibmopt 
-xmemalign=8s -xregs=frameptr -xtarget=native -xbuiltin=%all -library=sunperf" 
CPPFLAGS="-IInclude" OPT="" LDFLAGS="-v  -fsimple=0 -m64 -mt=yes -xbuiltin 
-xhwcprof -xF -xarch=native -xchip=native -fma=fused -g -xO5 -xlibmil -xlibmopt 
-xmemalign=8s -xbuiltin=%all -xregs=frameptr -xtarget=native -library=sunperf" 
CC=/opt/solarisstudio12.3/bin/cc 

(Due to indirect linker invocation via cc, I'm purposely duplicating CFLAGS <-> 
LDFLAGS for now.  I'll refine later.)

--

___
Python tracker 

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

[issue15956] backreference to named group does not work

[Steve Newcomb]

Steve Newcomb added the comment:

> But this way exists: (?P=startquote) is what you want.

I know how I missed it: I searched for "backref" in the documentation.  I did 
not find it in the discussion of the pattern language, because that word does 
not appear where  contributions are welcome.

See attached brief patch for the documentation.  It changes the example, adds a 
table of the three processing contexts in which named groups can be referenced, 
and accounts for users who, like me, may search for "backref".  (I tested 
everything.  I think it's correct.)

Thanks again for the advice, Amaury.

--
Added file: http://bugs.python.org/file27217/patch

___
Python tracker 

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

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

[Trent Nelson]

New submission from Trent Nelson:

All my slaves' /tmp's are polluted with regrtest fluff.  I haven't checked yet, 
but I presume no cleanup is done if a test/run fails.

nitrogen% find /tmp -user cpython 2> /dev/null | wc -l
197
netbsd51-x64-1$ find /tmp -user cpython 2> /dev/null | wc -l
 142
oxygen% find /tmp -user cpython 2> /dev/null | wc -l
456

Placeholder issue until it annoys me enough to patch.

--
assignee: trent
components: Build
messages: 170663
nosy: trent
priority: normal
severity: normal
status: open
title: Slaves don't seem to clean up their /tmp mess if a step fails.
type: behavior

___
Python tracker 

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

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

[Charles-François Natali]

Charles-François Natali added the comment:

> What's wrong with working around this bug by reading a smaller amount?
> How much data is there supposed to be?

Nothing, except that there are probably other places in the stdlib
where we can get bitten by this bug. Note that this should eventually
be done for another reason, see http://bugs.python.org/issue15918

> In the work-around, we need to watch out for what 'man 2 read' on Mac OS 
> refers to as
> "normal file":

There's nothing special actually.
This precision concerning normal file is OS-X specific, POSIX makes no
such guarantee: you can always get a short read (e.g. because of
signal delivery), so one should always call read() in a loop.

--

___
Python tracker 

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

[issue15039] module/ found before module.py when both are in the CWD

[Eric V. Smith]

Changes by Eric V. Smith :


--
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

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

[Larry Hastings]

Larry Hastings added the comment:

Lgtm. 

Trent Nelson  wrote:

>
>Trent Nelson added the comment:
>
>Easy fix, cast AT_FDCWD to (int):
>
>
>% hg diff
>diff -r 3a880d640981 Modules/posixmodule.c
>--- a/Modules/posixmodule.c Tue Sep 18 07:21:18 2012 +0300
>+++ b/Modules/posixmodule.c Tue Sep 18 16:04:58 2012 +
>@@ -414,7 +414,14 @@
> 
> 
> #ifdef AT_FDCWD
>-#define DEFAULT_DIR_FD AT_FDCWD
>+/*
>+ * Why the (int) cast?  Solaris 10 defines AT_FDCWD as 0xffd19553 (-3041965);
>+ * without the int cast, the value gets interpreted as uint (4291925331),
>+ * which doesn't play nicely with all the initializer lines in this file that
>+ * look like this:
>+ *  int dir_fd = DEFAULT_DIR_FD;
>+ */
>+#define DEFAULT_DIR_FD (int)AT_FDCWD
> #else
> #define DEFAULT_DIR_FD (-100)
> #endif
>
>
>The cast is harmless on other platforms that use an actual integer (rather 
>than a hex representation).
>
>Any objections?
>
>--
>
>___
>Python tracker 
>
>___

--
title: AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings. -> 
AT_FDCWD is 0xffd19553 on Solaris 10,   resulting in compiler warnings.

___
Python tracker 

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

[issue15956] backreference to named group does not work

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc added the comment:

Thanks for the patch!  The new formulation looks much better, but I'll let a 
native speaker have another check.

Some comments: I preferred the previous example "" because it's not obvious 
what \042\047 is. And a bullet list would be less heavyweight IMO.
(Also please use "diff -u"; without context, the patch cannot be applied 
automatically)

--

___
Python tracker 

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

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

[R. David Murray]

R. David Murray added the comment:

Cleanup on test failure is supposed to be done.  Cleanup on crash or buildbot 
timeout isn't done as far as I know (and that was a concern I had with the 
changes made to support.TESTFN and the cwd, but I didn't articulate it very 
well).  

If you find tests that do no clean up on error, that's definitely a bug and we 
should fix them.

--
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

[issue15968] Incorporate Tcl/Tk/Tix into the Windows build process

[Jeremy Kloth]

New submission from Jeremy Kloth:

This patch incorporates Tcl/Tk/Tix into the MSVC build in the same fashion as 
OpenSSL has been done.

Highlights:
- A new project, tcltk, is added that simply calls the Python script 
build_tkinter.py to build the externals.
- New helper module PCbuild/buildlib.py to parse and evaluate the MSBuild 
property files.
- build_tkinter.py is updated to use MSBuild properties for locating the 
sources.
- The tcltk output directory is now inside the PCbuild directory to enable 
different Tcl/Tk/Tix versions for different Python versions

--
components: Build
hgrepos: 149
messages: 170668
nosy: jkloth
priority: normal
severity: normal
status: open
title: Incorporate Tcl/Tk/Tix into the Windows build process
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

[issue15952] format(value) and value.__format__() behave differently with unicode format

[Chris Jerdonek]

Chris Jerdonek added the comment:

Here is a proposed patch.

One note on the patch.  I feel the second sentence of the note is worth adding 
because value.__format__() departs from what PEP 3101 says:

"Note for Python 2.x: The 'format_spec' argument will be either
a string object or a unicode object, depending on the type of the
original format string.  The __format__ method should test the type
of the specifiers parameter to determine whether to return a string or
unicode object.  It is the responsibility of the __format__ method
to return an object of the proper type."

The extra sentence will help in heading off and when responding to issues about 
value.__format__() that are similar to issue 15951.

--
keywords: +patch
stage:  -> patch review
Added file: http://bugs.python.org/file27218/issue-15952-1-branch-27.patch

___
Python tracker 

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

[issue15956] backreference to named group does not work

[Steve Newcomb]

Steve Newcomb added the comment:

> I preferred the previous example "" because it's not obvious what 
> \042\047 is. 

Yeah, but the example I wrote has an in-pattern backreference and a real reason 
to use one.

In the attached patch, I have changed [\042\047] to [\'\"].  That's certainly 
clearer for everyone who has not memorized the ASCII table in octal!  (Oops.)

> And a bullet list would be less heavyweight IMO.

Well... I rejected that choice because there would be no clarifying columnar 
distinction between contexts and syntaxes.  Personally, I think the table is 
clearer.  It makes it easier for users to find what they need know.

>(Also please use "diff -u"; without context, the patch cannot be applied 
>automatically)

Oops.  Attached.

--
Added file: http://bugs.python.org/file27219/patch

___
Python tracker 

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

[issue15952] format(value) and value.__format__() behave differently with unicode format

[Chris Jerdonek]

Chris Jerdonek added the comment:

To clarify, one of the sentences above should have read, "I feel the second 
sentence of the note *in the patch* was worth adding..." (not the second 
sentence of the PEP note I quoted).

--

___
Python tracker 

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

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

[Chris Jerdonek]

Chris Jerdonek added the comment:

To follow up on David's comment, the unit tests in the test suite aren't 
consistent in their treatment of temp directories (e.g. they don't use a common 
API or code path).  So it may be hard to address this globally short of wiping 
the entire temp directory (though I could be wrong).

I have a patch in issue 15415 to add a temp_dir() context manager to 
test.support (and consolidate with script_helper's) that would do such 
clean-up.  The module already has a temp_cwd(), but that context manager serves 
two purposes.

--
nosy: +cjerdonek

___
Python tracker 

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

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

[Vitaly]

Vitaly added the comment:

> Nothing, except that there are probably other places in the stdlib
> where we can get bitten by this bug. Note that this should eventually
> be done for another reason, see http://bugs.python.org/issue15918

For greatest benefit, I think that the work-around should be implemented in 
os.read()

--

___
Python tracker 

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

[issue15744] missing tests for {RawIO,BufferedIO,TextIO}.writelines

[Felipe Cruz]

Felipe Cruz added the comment:

Updated based on Pitrou comments

--
Added file: http://bugs.python.org/file27220/issue15744_v2.patch

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Richard Oudkerk]

Richard Oudkerk added the comment:

> You would need to call memory_release(). Perhaps we can just expose it on the
> C-API level as PyMemoryView_Release().

Should PyMemoryView_Release() release the _PyManagedBufferObject by doing 
mbuf_release(view->mbuf) even if view->mbuf->exports > 0?

Doing

  Py_TYPE(view->mbuf)->tp_clear((PyObject *)view->mbuf);

seems to have the desired effect of causing ValueError when I try to access any 
associated memoryview.

>  3) A piece of memory needs to be packaged as a memoryview with automatic
> cleanup in mbuf_dealloc():
>
>PyMemoryView_FromBufferWithCleanup() (proposed in msg169613)

Maybe this should also handle decrefing the base object (given a flag 
PyManagedBuffer_FreeObj).  I do worry about creating memoryviews that survive 
deallocation of the base object.

--

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[STINNER Victor]

Changes by STINNER Victor :


--
nosy: +haypo

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Antoine Pitrou]

Antoine Pitrou added the comment:

> So I think the combination of PyMemoryView_FromObject() with a call to
> PyMemoryView_Release() should indeed work here.

I don't think we want to expose a mutable bytes object to outside code, so IMO 
PyMemoryView_FromMemory() is preferrable.

--

___
Python tracker 

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

[issue15969] faulthandler: drop S from dump_tracebacks_later() function name to have consistent names

[STINNER Victor]

New submission from STINNER Victor:

If it is not too late, I would like to "fix" the name of two functions of the 
new faulthandler module before the release of Python 3.3 final. Changes:

 * dump_tracebacks_later() => dump_traceback_later()
 * cancel_dump_tracebacks_later() => cancel_dump_traceback_later()

The module has also a function dump_traceback() without S.

In an early version of the module (before it was integrated in Python 3.3), 
these functions only dumped the current thread. They are now dumping all 
threads by default, and I don't see the point of having an S anyway.

@Georg: Would you accept such change? The module is new in Python 3.3, and it 
is only a debug module, I don't expect anyone relying on its API right now.

--
components: Library (Lib)
files: faulthandler_without_s.patch
keywords: patch
messages: 170677
nosy: georg.brandl, haypo
priority: release blocker
severity: normal
status: open
title: faulthandler: drop S from dump_tracebacks_later() function name to have 
consistent names
versions: Python 3.3
Added file: http://bugs.python.org/file27221/faulthandler_without_s.patch

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Stefan Krah]

Stefan Krah added the comment:

Richard Oudkerk  wrote:
> Should PyMemoryView_Release() release the _PyManagedBufferObject by doing 
> mbuf_release(view->mbuf) even if view->mbuf->exports > 0?

No, I think it should really just be a wrapper:

diff --git a/Objects/memoryobject.c b/Objects/memoryobject.c
--- a/Objects/memoryobject.c
+++ b/Objects/memoryobject.c
@@ -1093,6 +1093,12 @@
 return memory_release((PyMemoryViewObject *)self, NULL);
 }

+PyObject *
+PyMemoryView_Release(PyObject *m)
+{
+return memory_release((PyMemoryViewObject *)m, NULL);
+}
+

We decided in #10181 not to allow releasing a view with exports, since the
logic is already quite complex. Is there a reasonable expectation that
existing code creates memoryviews of the readinto() argument?

--

___
Python tracker 

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

[issue15969] faulthandler: drop S from dump_tracebacks_later() function name to have consistent names

[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

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

[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

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

[Arfrever Frehtes Taifersar Arahesis]

Changes by Arfrever Frehtes Taifersar Arahesis :


--
title: AT_FDCWD is 0xffd19553 on Solaris 10,resulting in compiler warnings. 
-> AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

___
Python tracker 

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

[issue15956] backreference to named group does not work

[Amaury Forgeot d'Arc]

Changes by Amaury Forgeot d'Arc :


--
assignee:  -> docs@python
nosy: +docs@python
stage: committed/rejected -> patch review

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Stefan Krah]

Stefan Krah added the comment:

Antoine Pitrou  wrote:
> I don't think we want to expose a mutable bytes object to outside code,
> so IMO PyMemoryView_FromMemory() is preferrable.

I agree, but PyMemoryView_FromMemory(PyBytes_AS_STRING(b), n, PyBUF_WRITE)
just hides the fact that a mutable bytes object is exposed.

Are we talking about a big speedup here or could we perhaps just keep
the existing code?

--

___
Python tracker 

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

[issue15956] backreference to named group does not work

[Andrew Svetlov]

Changes by Andrew Svetlov :


--
nosy: +asvetlov

___
Python tracker 

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

[issue8425] a -= b should be fast if a is a small set and b is a large set

[STINNER Victor]

Changes by STINNER Victor :


--
versions: +Python 3.4 -Python 3.3

___
Python tracker 

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

[issue15964] SyntaxError in asdl when building 2.7 with system Python 3

[STINNER Victor]

Changes by STINNER Victor :


--
nosy: +haypo

___
Python tracker 

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

[issue15954] No error checking after using of the wcsxfrm()

[STINNER Victor]

Changes by STINNER Victor :


--
nosy: +haypo

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Antoine Pitrou]

Antoine Pitrou added the comment:

> Antoine Pitrou  wrote:
> > I don't think we want to expose a mutable bytes object to outside code,
> > so IMO PyMemoryView_FromMemory() is preferrable.
> 
> I agree, but PyMemoryView_FromMemory(PyBytes_AS_STRING(b), n, PyBUF_WRITE)
> just hides the fact that a mutable bytes object is exposed.

Except that the mutable bytes object is not exposed to any outside code,
so that weird behaviour can't be observed.

--

___
Python tracker 

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

[issue15903] Make rawiobase_read() read directly to bytes object

[Richard Oudkerk]

Richard Oudkerk added the comment:

> Are we talking about a big speedup here or could we perhaps just keep
> the existing code?

I doubt it is worth the hassle.  But I did want to know if there was a clean 
way to do what I wanted.

--

___
Python tracker 

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

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

[Mark Dickinson]

Changes by Mark Dickinson :


--
nosy: +brian.curtin

___
Python tracker 

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

[issue15964] SyntaxError in asdl when building 2.7 with system Python 3

[Christian Heimes]

Christian Heimes added the comment:

I think this might be related to #15923. It shouldn't be necessary to rebuild 
the AST definition unless you have modified the grammar and AST files.

--
nosy: +christian.heimes

___
Python tracker 

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

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

[Brian Curtin]

Changes by Brian Curtin :


--
assignee:  -> bquinlan
nosy: +bquinlan

___
Python tracker 

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

[issue13888] test_builtin failure when run after test_tk

[STINNER Victor]

STINNER Victor added the comment:

"python: ../../src/xcb_io.c:273: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed."

I get a similar XCB assertion error:
"xcb_io.c:221: poll_for_event: Assertion `(((long) (event_sequence) - (long) 
(dpy->request)) <= 0)' failed."

The problem is that a Tk thread is still alive while test_builtins is running. 
XInitThreads() must be the first call to the Xlib for multithreaded 
applications.

Extract of:
https://groups.google.com/forum/#!msg/comp.lang.tcl/gFcxwy9TxLc/drmHzhvM9YQJ

"3. Tk's thread support for unix/X11 is iffy.  There has been work done 
on making Tk thread safe, but Tk still doesn't call XInitThreads(), and 
probably won't anytime soon.  It seems that the XCB library has a 
superior implementation for threaded X11 interfaces anyway, so a 
complete rewrite would make more sense (to me).  Tk however can be used 
with threaded builds, and multiple threads, but only with a single 
thread using [package require Tk] as I understand it."

The correct fix is maybe to stop properly the Tk thread. (Example: Run test_tk 
in a subprocess? Call tk.quit()?)

--
components: +XML -Tests
nosy: +haypo

___
Python tracker 

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

[issue15144] Possible integer overflow in operations with addresses and sizes.

[STINNER Victor]

STINNER Victor added the comment:

> Perhaps the three new macros should be made available in a .h file?

Good idea. Maybe pymacros.h? These macros need to be documented (with a comment 
in the .h file)

--
nosy: +haypo

___
Python tracker 

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

[issue15923] Building from a fresh clone breaks on Parser/asdl_c.py

[STINNER Victor]

STINNER Victor added the comment:

See also #15964.

--
nosy: +haypo

___
Python tracker 

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

[issue13888] test_builtin failure when run after test_tk

[STINNER Victor]

Changes by STINNER Victor :


--
components: +Tests, Tkinter -XML

___
Python tracker 

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

[issue15964] SyntaxError in asdl when building 2.7 with system Python 3

[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

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

[Antoine Pitrou]

Antoine Pitrou added the comment:

The patch looks ok to me. At least passing "fn" as keyword arg should be fixed. 
Passing "self" as keyword arg admittedly sounds a bit awkward.

--
nosy: +pitrou

___
Python tracker 

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

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

[Antoine Pitrou]

Antoine Pitrou added the comment:

> All my slaves' /tmp's are polluted with regrtest fluff.

Which "regrtest fluff" exactly?

--
nosy: +pitrou

___
Python tracker 

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

[issue11664] Add patch method to unittest.TestCase

[Julian Berman]

Julian Berman added the comment:

It's slightly less confusing -- "Where do I patch" is the question that will 
never go away, and the fact that you don't have the `sys` module imported is a 
small hint that you should be doing patch(mymodule.sys, "path") not 
patch("sys.path"). Also, the fact that patch is more common doesn't reflect the 
fact that most of those times, patch.object would have worked as well, but it's 
longer to type (or people aren't as aware of it), since most of the time you're 
patching things in a module you've imported already (at least this is true of 
me, and I've started using patch.object whenever it works and only falling back 
on patch).

Also, Twisted's TestCase (which already has a method to implement patch) is 
functionally equivalent to patch.object, not patch, in case you wanted a 
precedent.

--

___
Python tracker 

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

[issue11664] Add patch method to unittest.TestCase

[Michael Foord]

Michael Foord added the comment:

Well, people vote with their code and find mock.patch vastly more useful than 
patch.object...

--

___
Python tracker 

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

[issue7712] Add a context manager to change cwd in test.test_support and run the test suite in a temp dir.

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +cjerdonek

___
Python tracker 

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

[issue15304] Wrong path in test.support.temp_cwd() error message

[Ezio Melotti]

Changes by Ezio Melotti :


--
assignee:  -> ezio.melotti
nosy: +ezio.melotti
type:  -> behavior
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

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

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +ezio.melotti, flox
type:  -> enhancement

___
Python tracker 

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

[issue11664] Add patch method to unittest.TestCase

[R. David Murray]

R. David Murray added the comment:

I actually agree with Julian here.  I much prefer patch.object and do my best 
to avoid mock.patch.  support.patch is also equivalent to patch.object and not 
patch.  That doesn't change the fact that other people prefer mock.patch, of 
course.

I think mock.patch is too "magical" for my taste.  There is something I don't 
like about the dynamic import, even though I can't really tell you what it is :)

--
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

[issue11664] Add patch method to unittest.TestCase

[Julian Berman]

Julian Berman added the comment:

With all due respect, your response pretty much ignored mine completely. That's 
OK, I've agreed with you that patch seems more common.

I'll point you additionally though to the fact that Éric's original post also 
used patch.object's semantics, as does test.test_support.swap_attr and patch.

I don't know how hard I can push here though, since again, this would be really 
confusing to have it have the same name.

--

___
Python tracker 

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

[issue11664] Add patch method to unittest.TestCase

[Chris Jerdonek]

Chris Jerdonek added the comment:

What about patch_object()?

--

___
Python tracker 

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

[issue15951] string.Formatter returns str for empty unicode template

[Chris Jerdonek]

Chris Jerdonek added the comment:

Attached is a proposed patch.

Some explanation behind the patch that stems from the above comments:

The following is an example of Formatter.format() returning str in the current 
implementation that would break if we made Formatter.format() return unicode 
whenever format_string is unicode:

>>> f.format(u"{0}", "\xc3\xa9")  # UTF-8 encoded "e-acute".
'\xc3\xa9'

(It would break with a UnicodeDecodeError because 'ascii' is the default 
encoding.)

Since we can't change Formatter.format(format_string) to return unicode 
whenever format_string is unicode without breaking existing code, I believe the 
best we can do is to document the departure from PEP 3101.  Since the caller 
has to handle return values of type str anyways, I don't think it helps to 
ensure that more return values are unicode.

--
Added file: http://bugs.python.org/file27222/issue-15951-2-branch27.patch

___
Python tracker 

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

[issue11664] Add patch method to unittest.TestCase

[Ezio Melotti]

Ezio Melotti added the comment:

IMHO a setattr-like API seems the obvious choice here, so that's what I would 
expect.  I haven't used mock, so I wasn't familiar with mock.patch, but after 
skimming through the mock docs a bit I think I have to agree with Julian and 
RDM.
In addition, I'm not sure we need TestCase.patch now that we have already have 
mock.patch(.object) in the stdlib.  If we still add it, it would probably make 
more sense as a "vanilla" patch that doesn't depend on mock.


> a helper TestCase.patch should delegate to unittest.mock.patch

Does it mean it will return MagicMocks?


> patch.object would have worked as well, but it's longer to type

If mock.patch requires a FQN to work the call might even be longer:
patch('package.subpackage.module.function') vs
patch.object(module, 'function', newfunc)
(assuming "from package.subpackage import module", which is not uncommon if we 
are testing that specific module)


> What about patch_object()?

patchobj()?

--

___
Python tracker 

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

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

[Ezio Melotti]

Ezio Melotti added the comment:

I think I'm -1 on this, for the following reasons:
 * it's less explicit;
 * it gives you less control (I'm thinking e.g. at the () added by 
:func:/:meth: but not :class:, so that :func:`int` and :class:`int` are 
rendered in different ways);
 * even though this might have been OK if we used it from the beginning, now we 
are using specific roles everywhere, and changing them will either result in a 
mass update or in a mixed style -- none of which are desirable;
 * if the mass update is done and later on we change our mind, it's difficult 
to switch back from `...` to :role:`...`.

Disabling `...` sounds OK to me (I don't think we have many left, if any).

--

___
Python tracker 

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

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

[Roundup Robot]

Roundup Robot added the comment:

New changeset 974a4cae6094 by Trent Nelson in branch 'default':
#15965: Explicitly cast AT_FDCWD as (int).
http://hg.python.org/cpython/rev/974a4cae6094

--
nosy: +python-dev

___
Python tracker 

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

[issue7665] test_urllib2 and test_ntpath fail if path contains "\"

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +haypo
stage: needs patch -> patch review

___
Python tracker 

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

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

[Trent Nelson]

Changes by Trent Nelson :


--
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

[issue11454] email.message import time

[Ezio Melotti]

Ezio Melotti added the comment:

re.compile seems twice as fast as pickle.loads:


import re
import pickle
import timeit

N = 10
s = "r = re.compile('[\\udc80-\\udcff]')"
t = timeit.Timer(s, 'import re')
print("%6.2f <- re.compile" % t.timeit(number=N))

s = "r = pickle.loads(p)"
p = pickle.dumps(re.compile('[\udc80-\udcff]'))
t = timeit.Timer(s, 'import pickle; from __main__ import p')
print("%6.2f <- pickle.loads" % t.timeit(number=N))


Result:
  5.59 <- re.compile
 11.04 <- pickle.loads


See also #2679.

--

___
Python tracker 

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

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

[Nick Coghlan]

Nick Coghlan added the comment:

The particular app that is getting affected is clearing out and rebuilding the 
logging configuration without restarting in response to a notification that the 
application config has changed. This was working OK on 2.6, but started 
misbehaving when ported to 2.7.

It's http://pypi.python.org/pypi/ConcurrentLogHandler that's calling 
self.stream.flush() inside release(), and I suspect that *is* a bug on that 
side as well.

It's also possible that we should just be skipping the use of 
ConcurrentLogHandler entirely on 2.7, but I haven't looked into the feasibility 
of that as yet.

This specific bug report is just because I noticed that the stdlib is *trying* 
to be tolerant of handler misbehaviour, but not quite succeeding in this 
particular case. Perhaps we should be writing something out to stderr when 
ignoring one of these errors?

--

___
Python tracker 

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

[issue15970] ElementTree HTML serialization incorrect for ,

[Joshua Biagio]

New submission from Joshua Biagio:

There seems to be a very minor bug in the ElementTree.py file, for the 
so-called 'empty' elements that are serialized without a closing tag. The 
HTML_EMPTY tuple/set is used to lookup these tags.

In the Lib/xml/etree/ElementTree.py file, the HTML_EMPTY tuple is created like:

HTML_EMPTY = ("area", "base", "basefont", "br", "col", "frame", "hr",
  "img", "input", "isindex", "link", "meta" "param")

There is a missing comma between "meta" and "param". I'm not sure if this is 
intended behavior.

The line should be replaced with:

HTML_EMPTY = ("area", "base", "basefont", "br", "col", "frame", "hr",
  "img", "input", "isindex", "link", "meta", "param")

--
components: Library (Lib), XML
messages: 170699
nosy: Joshua.Biagio
priority: normal
severity: normal
status: open
title: ElementTree HTML serialization incorrect for , 
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3

___
Python tracker 

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

[issue15971] Sporadic failure in test_dump_tracebacks_later_file (test_faulthandler)

[Ezio Melotti]

New submission from Ezio Melotti:

Seen on 
http://buildbot.python.org/all/builders/AMD64%20Lion%203.x/builds/428/steps/test/logs/stdio

==
FAIL: test_dump_tracebacks_later_file (test.test_faulthandler.FaultHandlerTests)
--
Traceback (most recent call last):
  File 
"/Users/ambv/Buildbot/3.x.langa-lion/build/Lib/test/test_faulthandler.py", line 
490, in test_dump_tracebacks_later_file
self.check_dump_tracebacks_later(file=True)
  File 
"/Users/ambv/Buildbot/3.x.langa-lion/build/Lib/test/test_faulthandler.py", line 
476, in check_dump_tracebacks_later
filename, loops)
  File 
"/Users/ambv/Buildbot/3.x.langa-lion/build/Lib/test/test_faulthandler.py", line 
460, in _check_dump_tracebacks_later
self.assertRegex(trace, regex)
AssertionError: Regex didn't match: '^Timeout \\(0:00:00.50\\)!\\nThread 
0x[0-9a-f]+:\\n  File "", line 9 in func\n  File "", line 20 in 
$' not found in 'Timeout (0:00:00.50)!\nThread 
0x7fff77d85960:\n  File "", line 10 in func\n  File "", 
line 20 in '

--
Ran 30 tests in 126.504s

The regex expects the failure to be at "line 9 in func", but the failure 
happens at "line 10".

--
assignee: haypo
components: Tests
messages: 170700
nosy: ezio.melotti, haypo, lukasz.langa
priority: normal
severity: normal
stage: needs patch
status: open
title: Sporadic failure in test_dump_tracebacks_later_file (test_faulthandler)
type: behavior
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

[issue7559] TestLoader.loadTestsFromName swallows import errors

[Julian Berman]

Changes by Julian Berman :


--
nosy: +Julian

___
Python tracker 

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

[issue15970] ElementTree HTML serialization incorrect for ,

[Roundup Robot]

Roundup Robot added the comment:

New changeset 3498ffd3cdee by Ezio Melotti in branch '2.7':
#15970: xml.etree.ElementTree now serializes correctly the empty HTML elements 
"meta" and "param".
http://hg.python.org/cpython/rev/3498ffd3cdee

New changeset 17c528cff63f by Ezio Melotti in branch '3.2':
#15970: xml.etree.ElementTree now serializes correctly the empty HTML elements 
"meta" and "param".
http://hg.python.org/cpython/rev/17c528cff63f

New changeset 19c74cadea95 by Ezio Melotti in branch 'default':
#15970: merge with 3.2.
http://hg.python.org/cpython/rev/19c74cadea95

--
nosy: +python-dev

___
Python tracker 

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

[issue15970] ElementTree HTML serialization incorrect for ,

[Ezio Melotti]

Ezio Melotti added the comment:

Fixed, thanks for the report!

--
assignee:  -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type:  -> behavior
versions:  -Python 2.6, Python 3.1

___
Python tracker 

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