[ python-Bugs-223616 ] compiler package needs better documentation.

2007-04-10 Thread SourceForge.net 
Bugs item #223616, was opened at 2000-11-27 15:33
Message generated for change (Comment added) made by facundobatista
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=223616&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Feature Request
>Status: Closed
>Resolution: Fixed
Priority: 6
Private: No
Submitted By: Fred L. Drake, Jr. (fdrake)
Assigned to: Jeremy Hylton (jhylton)
Summary: compiler package needs better documentation.

Initial Comment:
The compiler package is not documented; this needs to be done before tools are 
likely to be written on top of it.

--

>Comment By: Facundo Batista (facundobatista)
Date: 2007-04-10 10:21

Message:
Logged In: YES 
user_id=752496
Originator: NO

The SVN log reflects that the docs *have* been moved into the Library
Reference, and that they have been corrected and polished.

Fred, you said they needed polishing in December 2001. From then,
corrections have been made from Georg, Raymond, Brett and edloper.

I'm closing this, but feel free to reopen it if you think that this docs
*still* need more polishing.

Regards,

--

Comment By: Facundo Batista (facundobatista)
Date: 2007-03-28 18:00

Message:
Logged In: YES 
user_id=752496
Originator: NO

This is one of the oldest bugs we have...

As the compiler package surely got revised with the inclusion of AST, and
the bug was only to remember about polishing... this still needs to be
open?


--

Comment By: Jeremy Hylton (jhylton)
Date: 2002-03-01 19:38

Message:
Logged In: YES 
user_id=31392

jeremy, get your butt in gear on this!


--

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-12-21 15:19

Message:
Logged In: YES 
user_id=3066

I'll note that Jeremy has written basic docs, and they are
in the Library Reference.  But he really needs to polish
them a bit as well, so this stays open but gets a new summary.

--

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-08-10 18:56

Message:
Logged In: YES 
user_id=3066

Jeremy said he'd work on this next week, so I'm bumping the
priority as a reminder.

--

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-01-08 00:48

Message:
Jeremy -- is there anything that can be done to make it easier for you to
get this done?  I think these should really be documented and moved into
the library.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=223616&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-223616 ] compiler package needs better documentation.

2007-04-10 Thread SourceForge.net 
Bugs item #223616, was opened at 2000-11-27 13:33
Message generated for change (Comment added) made by fdrake
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=223616&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Feature Request
Status: Closed
Resolution: Fixed
Priority: 6
Private: No
Submitted By: Fred L. Drake, Jr. (fdrake)
Assigned to: Jeremy Hylton (jhylton)
Summary: compiler package needs better documentation.

Initial Comment:
The compiler package is not documented; this needs to be done before tools are 
likely to be written on top of it.

--

>Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2007-04-10 10:00

Message:
Logged In: YES 
user_id=3066
Originator: YES

I think this is fine, Facundo.  All docs need polishing, but that's not a
bug so long as they're complete, accurate, and readable.

Thanks for checking on this.

--

Comment By: Facundo Batista (facundobatista)
Date: 2007-04-10 09:21

Message:
Logged In: YES 
user_id=752496
Originator: NO

The SVN log reflects that the docs *have* been moved into the Library
Reference, and that they have been corrected and polished.

Fred, you said they needed polishing in December 2001. From then,
corrections have been made from Georg, Raymond, Brett and edloper.

I'm closing this, but feel free to reopen it if you think that this docs
*still* need more polishing.

Regards,

--

Comment By: Facundo Batista (facundobatista)
Date: 2007-03-28 17:00

Message:
Logged In: YES 
user_id=752496
Originator: NO

This is one of the oldest bugs we have...

As the compiler package surely got revised with the inclusion of AST, and
the bug was only to remember about polishing... this still needs to be
open?


--

Comment By: Jeremy Hylton (jhylton)
Date: 2002-03-01 17:38

Message:
Logged In: YES 
user_id=31392

jeremy, get your butt in gear on this!


--

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-12-21 13:19

Message:
Logged In: YES 
user_id=3066

I'll note that Jeremy has written basic docs, and they are
in the Library Reference.  But he really needs to polish
them a bit as well, so this stays open but gets a new summary.

--

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-08-10 17:56

Message:
Logged In: YES 
user_id=3066

Jeremy said he'd work on this next week, so I'm bumping the
priority as a reminder.

--

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-01-07 22:48

Message:
Jeremy -- is there anything that can be done to make it easier for you to
get this done?  I think these should really be documented and moved into
the library.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=223616&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-1696740 ] README is referencing obsolete? http://starship.python.net

2007-04-10 Thread SourceForge.net 
Bugs item #1696740, was opened at 2007-04-09 02:58
Message generated for change (Comment added) made by gagenellina
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1696740&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jiri Navratil (plavcik)
Assigned to: Nobody/Anonymous (nobody)
Summary: README is referencing obsolete? http://starship.python.net

Initial Comment:
In README file obtained 09.04.2004 from Python SVN HEAD via svn is referenced 

There's also a Python community web site at
http://starship.python.net/.

I can't open this site. I'm getting

unable to find IP address for starship.python.net

Is this information obsolete?


--

Comment By: Gabriel Genellina (gagenellina)
Date: 2007-04-10 11:06

Message:
Logged In: YES 
user_id=479790
Originator: NO

No, the site had some problems but it's up and running again.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1696740&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-1697782 ] types.InstanceType is missing but used by pydoc

2007-04-10 Thread SourceForge.net 
Bugs item #1697782, was opened at 2007-04-10 17:55
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1697782&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 3000
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Christian Heimes (tiran)
Assigned to: Nobody/Anonymous (nobody)
Summary: types.InstanceType is missing but used by pydoc

Initial Comment:
>>> help(callable.__call__)
Traceback (most recent call last):
  File "", line 1, in 
  File "/home/heimes/dev/python/p3yk/Lib/site.py", line 348, in __call__
return pydoc.help(*args, **kwds)
  File "/home/heimes/dev/python/p3yk/Lib/pydoc.py", line 1658, in __call__
self.help(request)
  File "/home/heimes/dev/python/p3yk/Lib/pydoc.py", line 1702, in help
else: doc(request, 'Help on %s:')
  File "/home/heimes/dev/python/p3yk/Lib/pydoc.py", line 1477, in doc
desc = describe(object)
  File "/home/heimes/dev/python/p3yk/Lib/pydoc.py", line 1436, in describe
if type(thing) is types.InstanceType:
AttributeError: 'module' object has no attribute 'InstanceType'


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1697782&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-1697820 ] __getslice__ still used in built-in types

2007-04-10 Thread SourceForge.net 
Bugs item #1697820, was opened at 2007-04-10 19:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1697820&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Torsten Bronger (bronger)
Assigned to: Nobody/Anonymous (nobody)
Summary: __getslice__ still used in built-in types

Initial Comment:
In the Python language reference 
, after the sentence

"""Deprecated since release 2.0. Support slice objects as parameters to the 
__getitem__() method."""

I suggest the following addition:

"""However, built-in types in CPython currently still implement __getslice__.  
Therefore, you have to override it in derived classes when implementing 
slicing."""

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1697820&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-1697916 ] Segfaults on memory error

2007-04-10 Thread SourceForge.net 
Bugs item #1697916, was opened at 2007-04-10 21:47
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1697916&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: STINNER Victor (haypo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Segfaults on memory error

Initial Comment:
Hi, I'm playing with resource.setrlimit(resource.RLIMIT_AS) to limit memory 
usage during fuzzing tests. It works quite well but Python crashs sometimes 
(with SEGFAULT).

I downloaded Python source code and recompiled it with EXTRA_FLAGS="-g -O0" to 
find errors. I found three bugs and wrote a patch for all of them.

Comments:
* Objects/exceptions.c:33: allocation may returns NULL on memory error
* Objects/longobject.c:2511: long_divrem() may allocate new long integers but 
l_divmod() doesn't check that div and mod are not NULL
* Objects/object.c:1284: problem with NULL mro. I don't understand how mro 
works, but I think that the error may be catched when mro is assigned. Problem: 
where is it done? in Objects/typeobject.c?

So don't apply my patch directly: fix for object.c may be wrong.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1697916&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-1697943 ] msgfmt cannot cope with BOM

2007-04-10 Thread SourceForge.net 
Bugs item #1697943, was opened at 2007-04-10 22:58
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1697943&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Demos and Tools
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Christoph Zwerschke (cito)
Assigned to: Nobody/Anonymous (nobody)
Summary: msgfmt cannot cope with BOM

Initial Comment:
If a .po file has a BOM (byte order mark) at the beginning, as is often the 
case for utf-8 files created on Windows, msgfmt.py complines about a syntax 
error.

The attached patch fixes this problem.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1697943&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[ python-Bugs-1698167 ] xml.etree document element.tag

2007-04-10 Thread SourceForge.net 
Bugs item #1698167, was opened at 2007-04-11 06:25
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1698167&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: paul rubin (phr)
Assigned to: Nobody/Anonymous (nobody)
Summary: xml.etree document element.tag

Initial Comment:
The xml.etree docs vaguely mention an implementation-dependent Element 
interface without describing it in any detail.  I could not figure out from the 
docs how to get the tag name of an element returned from (say) the getiterator 
interface.  That is, for an element like , I wanted the string "foo".  
Examining the library source showed that e.tag does the job, at least some of 
the time, and that was enough to get my app working.  Could the actual 
situation please be documented--thanks.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1698167&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com