[issue20347] dir(__future__) gives segfault on OS X in 3.2 and 3.3

2014-01-22 Thread Christopher the Magnificent
New submission from Christopher the Magnificent: On OS X 10.9.1 This works: Python 2.7.5 (default, Aug 25 2013, 00:04:04) [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on darwin Type help, copyright, credits or license for more information. import __future__ dir(__future__

[issue16267] order of decorators @abstractmethod and @classmethod is significant (is not documented to be in @abstractclassmethod which advises their combined use)

2012-10-17 Thread Christopher the Magnificent
New submission from Christopher the Magnificent: This may be an issue with the interpreter behavior or it may be a documentation issue. Note: I only selected Python 3.3 as the version, but it probably affects MANY other Python versions. Python 3.3.0 (v3.3.0:bd8afb90ebf2, Sep 29 2012, 01:25

[issue16268] dir(closure) claims that a closure has no __dir__, only to work later after manually invoking __dir__ from its type

2012-10-17 Thread Christopher the Magnificent
New submission from Christopher the Magnificent: This is really short, you should spot the inconsistency in the result of the same function call fairly easily. Python 3.3.0 (v3.3.0:bd8afb90ebf2, Sep 29 2012, 01:25:11) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin Type help, copyright

[issue16267] order of decorators @abstractmethod and @classmethod is significant (is not documented to be in @abstractclassmethod which advises their combined use)

2012-10-17 Thread Christopher the Magnificent
Christopher the Magnificent added the comment: As Darren Dale pointed out, it looks like this is a (partial) documentation issue. I think it's plausible that someone like me, who has used abstractmethod by itself, would read the docs for abstractclassmethod and not re-read the docs

[issue16271] weird dual behavior with changing __qualname__; different values observed through attribute and descriptor

2012-10-17 Thread Christopher the Magnificent
New submission from Christopher the Magnificent: The output below is NOT typed at the Python interactive interpeter. The shows what is being evaluated and the line below it shows what the result it. The output gets generated here: (lines 418-449 of the attached file) def

[issue15343] pydoc -w package writes out page with empty Package Contents section

2012-07-17 Thread Christopher the Magnificent
Christopher the Magnificent ultimate.mac.fana...@gmail.com added the comment: ISSUE CONFIRMED FIXED ON MY END, AND MANY THANKS I downloaded, compiled, and installed the latest Python 3.3 beta on my machine with Mercurial, and can confirm that the problem is no longer presenting itself. Thank

[issue15343] pydoc -w package write out page with empty package contents section

2012-07-12 Thread Christopher the Magnificent
New submission from Christopher the Magnificent ultimate.mac.fana...@gmail.com: Let there be a folder testpkg contained in $SOME_DIR with three empty files: __init__.py, bob.py, and sally.py If I run pydoc3.2 -w testpkg inside $SOME_DIR, it will output the file $SOME_DIR/testpkg.html

[issue15343] pydoc -w package writes out page with empty Package Contents section

2012-07-12 Thread Christopher the Magnificent
Changes by Christopher the Magnificent ultimate.mac.fana...@gmail.com: -- title: pydoc -w package writes out page with empty package contents section - pydoc -w package writes out page with empty Package Contents section ___ Python tracker rep

[issue15343] pydoc -w package writes out page with empty package contents section

2012-07-12 Thread Christopher the Magnificent
Changes by Christopher the Magnificent ultimate.mac.fana...@gmail.com: -- title: pydoc -w package write out page with empty package contents section - pydoc -w package writes out page with empty package contents section ___ Python tracker rep

[issue13581] help() appears to be broken; doesn't display __doc__ for class type when called as help(type)

2011-12-11 Thread Christopher the Magnificent
New submission from Christopher the Magnificent ultimate.mac.fana...@gmail.com: observe help(type) and type.__doc__ in Python 3.1: help(type) Help on class type in module builtins: class type(object) | type(object) - the object's type | type(name, bases, dict) - a new type

[issue8030] documentation bugs and improvements

2010-02-28 Thread Christopher the Magnificent
New submission from Christopher the Magnificent ultimate.mac.fana...@gmail.com: Help for list looks like this: help(list) class list(object) | list() - new list | list(sequence) - new list initialized from sequence's items | Help for dict looks like