[issue14932] Python 3.3.0a3 build fails on MacOS 10.7 with XCode 4.3.2

[Thomas Robitaille]

New submission from Thomas Robitaille :

I can build Python 2.6 to 3.2 on MacOS 10.7 with XCode 4.3.2 using solely:

./configure
make

But if I do this with Python 3.3 alpha 3 I get the following error:

gcc   -framework CoreFoundation -o python.exe Modules/python.o 
libpython3.3m.a -ldl  -framework CoreFoundation 
./python.exe -SE -m sysconfig --generate-posix-vars
Could not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
python.exe(92825) malloc: *** mmap(size=7310873954244194304) failed (error 
code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Could not import runpy module
make: *** [Lib/_sysconfigdata.py] Segmentation fault: 11

The full log is attached.

--
components: Installation
files: python3.3_log
messages: 161765
nosy: Thomas.Robitaille
priority: normal
severity: normal
status: open
title: Python 3.3.0a3 build fails on MacOS 10.7 with XCode 4.3.2
versions: Python 3.3
Added file: http://bugs.python.org/file25743/python3.3_log

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

[issue14932] Python 3.3.0a3 build fails on MacOS 10.7 with XCode 4.3.2

[Thomas Robitaille]

Changes by Thomas Robitaille :


--
type:  -> compile error

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

[issue14932] Python 3.3.0a3 build fails on MacOS 10.7 with XCode 4.3.2

[Thomas Robitaille]

Thomas Robitaille  added the comment:

Thanks for the quick reply - wouldn't it make sense to add a directive to the 
configure script so that if the compiler matches 
'i686-apple-darwin11-llvm-gcc-4.2', clang is used instead?

--

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

[issue20150] API breakage in string formatting with :s option

[Thomas Robitaille]

New submission from Thomas Robitaille:

The following code:

>>> "{0:s}".format([1,2,3])

no longer works in Python 3.4b1, and gives the following exception:

>>> "{0:s}".format([1,2,3])
Traceback (most recent call last):
  File "", line 1, in 
TypeError: non-empty format string passed to object.__format__

This worked previously in Python 2.6-3.3:

>>> "{0:s}".format([1,2,3])
'[1, 2, 3]'

If this is a deliberate change, it should be included in the 'What's new in 
Python 3.4'

--
components: Interpreter Core
messages: 207459
nosy: Thomas.Robitaille
priority: normal
severity: normal
status: open
title: API breakage in string formatting with :s option
versions: Python 3.4

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

[issue28835] Change in behavior when overriding warnings.showwarning and with catch_warnings(record=True)

[Thomas Robitaille]

New submission from Thomas Robitaille:

In Python 3.5, the following code:

import warnings

def deal_with_warning(*args, **kwargs):
print("warning emitted")

with warnings.catch_warnings(record=True):
warnings.showwarning = deal_with_warning
warnings.warn("This is a warning")

results in "warning emitted" being printed to the terminal.

In Python 3.6 however (at least in 3.6b1), nothing is printed, meaning that 
``deal_with_warning`` is not getting called. I bisected the CPython history and 
tracked it down to the changes in this issue:

https://bugs.python.org/issue26568

However it doesn't look like this was an intentional change in behavior, since 
it says in the description of that issue:

"For backward compatibility, warnings.showmsg() calls warnings.showwarning() if 
warnings.showwarning() was replaced. Same for warnings.formatmsg(): call 
warnings.formatwarning() if replaced."

So I believe this is a bug? (since backward-compatibility is not preserved). If 
not, should the change in behavior be mentioned in the changelog?

--
messages: 282056
nosy: Thomas.Robitaille
priority: normal
severity: normal
status: open
title: Change in behavior when overriding warnings.showwarning and with 
catch_warnings(record=True)
versions: Python 3.6

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