[ python-Bugs-1257687 ] Solaris 8 declares gethostname().
Bugs item #1257687, was opened at 2005-08-12 11:00 Message generated for change (Comment added) made by deragon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1257687&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: Build Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Hans Deragon (deragon) Assigned to: Nobody/Anonymous (nobody) Summary: Solaris 8 declares gethostname(). Initial Comment: In portpy.h line 377, we find: #ifdef SOLARIS /* Unchecked */ extern int gethostname(char *, int); #endif Well, on Solaris 8, that function is declared in /usr/include/unistd.h, thus a conflict. In unistd.h, there are a few #ifdef prior the declaration, so there might be some situation where the function is not declared. Of course, I cannot copy and paste the relevant section of unistd.h because of copyright. You might want to ask Sun Microsystem a copy of this file to patch this problem. My work around was to comment the above code in portpy.h. -- >Comment By: Hans Deragon (deragon) Date: 2005-08-14 06:35 Message: Logged In: YES user_id=148726 When compiling beecrypt, it complained that gethostname() was declared twice. Seams that beecrypt was compiling something for python and thus included pyport.h. At the same time, it was including unistd.h. That cause beecrypt compilation to halt with an error. -- Comment By: Martin v. Löwis (loewis) Date: 2005-08-13 10:05 Message: Logged In: YES user_id=21627 What precise problem does this cause? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1257687&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1258922 ] "it's" vs. "its" typo in Language Reference
Bugs item #1258922, was opened at 2005-08-14 13:00 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=1258922&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.4 Status: Open Resolution: None Priority: 5 Submitted By: Wolfgang Petzold (wolpertinger) Assigned to: Nobody/Anonymous (nobody) Summary: "it's" vs. "its" typo in Language Reference Initial Comment: Python 2.4.1 OS: All In section 2.3.2 "Reserved classes of identifiers", second item "__*__", the term "by the interpreter and it's implementation" should by changed to "by the interpreter and its implementation". We are talking about the implementation of the interpreter, and "it's"="it is" is not appropriate here. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1258922&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1258922 ] "it's" vs. "its" typo in Language Reference
Bugs item #1258922, was opened at 2005-08-14 13:00 Message generated for change (Comment added) made by wolpertinger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1258922&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.4 Status: Open Resolution: None Priority: 5 Submitted By: Wolfgang Petzold (wolpertinger) Assigned to: Nobody/Anonymous (nobody) Summary: "it's" vs. "its" typo in Language Reference Initial Comment: Python 2.4.1 OS: All In section 2.3.2 "Reserved classes of identifiers", second item "__*__", the term "by the interpreter and it's implementation" should by changed to "by the interpreter and its implementation". We are talking about the implementation of the interpreter, and "it's"="it is" is not appropriate here. -- >Comment By: Wolfgang Petzold (wolpertinger) Date: 2005-08-14 13:19 Message: Logged In: YES user_id=1272126 I've just browsed through the CVS web interface and found the typo already fixed in revision 1.58 of ref2.tex (on the MAIN branch). That should change the status of this bug report, but I am not sure what to. "Pending/Fixed"? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1258922&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1258922 ] "it's" vs. "its" typo in Language Reference
Bugs item #1258922, was opened at 2005-08-14 13:00 Message generated for change (Comment added) made by birkenfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1258922&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.4 >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Wolfgang Petzold (wolpertinger) Assigned to: Nobody/Anonymous (nobody) Summary: "it's" vs. "its" typo in Language Reference Initial Comment: Python 2.4.1 OS: All In section 2.3.2 "Reserved classes of identifiers", second item "__*__", the term "by the interpreter and it's implementation" should by changed to "by the interpreter and its implementation". We are talking about the implementation of the interpreter, and "it's"="it is" is not appropriate here. -- >Comment By: Reinhold Birkenfeld (birkenfeld) Date: 2005-08-14 14:38 Message: Logged In: YES user_id=1188172 It'll be "Out of Date", then. ;-) -- Comment By: Wolfgang Petzold (wolpertinger) Date: 2005-08-14 13:19 Message: Logged In: YES user_id=1272126 I've just browsed through the CVS web interface and found the typo already fixed in revision 1.58 of ref2.tex (on the MAIN branch). That should change the status of this bug report, but I am not sure what to. "Pending/Fixed"? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1258922&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1258986 ] Makefile ignores $CPPFLAGS
Bugs item #1258986, was opened at 2005-08-14 15:11 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=1258986&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: Build Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Dirk Pirschel (pirschel) Assigned to: Nobody/Anonymous (nobody) Summary: Makefile ignores $CPPFLAGS Initial Comment: Makefile ignores $CPPFLAGS Environment variable. Solution: patch Makefile.pre.in with - snip - 59c59 < CPPFLAGS= -I. -I$(srcdir)/Include --- > CPPFLAGS= -I. -I$(srcdir)/Include @CPPFLAGS@ - snip - -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1258986&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1256786 ] slice object uses -1 as exclusive end-bound
Bugs item #1256786, was opened at 2005-08-11 16:08 Message generated for change (Comment added) made by mwh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1256786&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.4 Status: Open Resolution: None Priority: 5 Submitted By: Bryan G. Olson (bryango) Assigned to: Michael Hudson (mwh) Summary: slice object uses -1 as exclusive end-bound Initial Comment: The slice object passed to __getitem__ or __setitem__ reports an incorrect 'stop' value when the step is negative and the slice includes the 0 index. If one then actually tries to slice with what slice.indices returns, the result is wrong. Here's a demo: class BuggerAll: def __init__(self, somelist): self.sequence = somelist[:] def __getitem__(self, key): if isinstance(key, slice): start, stop, step = key.indices(len(self.sequence)) # print 'Slice says start, stop, step are:', start, stop, step return self.sequence[start : stop : step] print range(10) [None : None : -2] print BuggerAll(range(10))[None : None : -2] The above should print the same sequence twice, but actually prints: [9, 7, 5, 3, 1] [] Un-commenting the print statement in __getitem__ shows: Slice says start, stop, step are: 9 -1 -2 The problem is the stop value of -1. The slice object seems to think that -1 is a valid exclusive-end-bound, but when slicing, Python interprets negative numbers as an offset from the high end of the sequence. That is, range(10)[9 : -1 : -2] is the same as, range(10)[[9 : 9 : -2] which is the empty list. So what should the slice.indices return in this case, so that slicing with the returned values will work correctly? My experiments indicate: The start value can be any of: None, any integer >= 9, -1 The stop value can be either: None, any integer <= -11 Step is correct; it must be:-2 My favorite choice here is (9, None, -2). The doc for slice.indices currently says: This method takes a single integer argument /length/ and computes information about the extended slice that the slice object would describe if applied to a sequence of length items. It returns a tuple of three integers; respectively these are the /start/ and /stop/ indices and the /step/ or stride length of the slice. Missing or out-of-bounds indices are handled in a manner consistent with regular slices. http://docs.python.org/ref/types.html So using (9, None, -2) would require changing both the code and the doc (because None is not an integer). A stop value of -11 (or less) would require changing only the code. -- >Comment By: Michael Hudson (mwh) Date: 2005-08-14 20:07 Message: Logged In: YES user_id=6656 Did you see my follow up on clpy? -- Comment By: Michael Hudson (mwh) Date: 2005-08-12 14:02 Message: Logged In: YES user_id=6656 This is clearly in my area. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1256786&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[ python-Bugs-1259434 ] Tix CheckList 'radio' option cannot be changed
Bugs item #1259434, was opened at 2005-08-14 20:09 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=1259434&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: Tkinter Group: Python 2.4 Status: Open Resolution: None Priority: 5 Submitted By: Raymond Maple (ray_maple) Assigned to: Martin v. Löwis (loewis) Summary: Tix CheckList 'radio' option cannot be changed Initial Comment: The 'radio' option to the Tix.CheckList widget cannot be set. Attempting to change the option during widget creation results in the following error: _tkinter.TclError: cannot assigned to static variable "-radio" The radio option is declared static in the Tix tcl library, and must be set at widget creation time. The radio option is not included in the list of static options passed to TixWidget.__init__ from CheckList.__init__ in file Tix.py. Solution: Add 'radio' to the list of static options passed to TixWidget.__init__ in Tix.py. Output from diff -C 1: *** 1562,1564 TixWidget.__init__(self, master, 'tixCheckList', !['options'], cnf, kw) self.subwidget_list['hlist'] = _dummyHList(self, 'hlist') --- 1562,1564 TixWidget.__init__(self, master, 'tixCheckList', !['options','radio'], cnf, kw) self.subwidget_list['hlist'] = _dummyHList(self, 'hlist') -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1259434&group_id=5470 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
