[issue5537] LWPCookieJar cannot handle cookies with expirations of 2038 or greater on 32-bit platforms

2011-02-18 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: While it is unlikely that a purely numeric format such as "%Y-%m-%d %H:%M:%S" will be locale dependent, it is possible that some pre-C99 systems would format dates using exotic digits is some locales. Given that format is so simple, I woul

[issue5537] LWPCookieJar cannot handle cookies with expirations of 2038 or greater on 32-bit platforms

2011-02-18 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Fri, Feb 18, 2011 at 11:04 AM, STINNER Victor wrote: .. > If datetime.strftime() is not reliable, we should maybe fix it instead of > using a workaround? The real fix would be to rewrite strftime so that it does not call system strftime

[issue2844] int() lies about base parameter

2008-05-13 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: The same issue is present in long_new: >>> long('42', -909) 42L I don't see why any magic value is needed, 10 would do the trick. -- nosy: +belopolsky __ Tra

[issue2844] int() lies about base parameter

2008-05-13 Thread Alexander Belopolsky
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: -- keywords: +patch Added file: http://bugs.python.org/file10316/issue2844.diff __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2844] int() lies about base parameter

2008-05-13 Thread Alexander Belopolsky
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: -- versions: +Python 2.6, Python 3.0 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2844> __ _

[issue2844] int() lies about base parameter

2008-05-13 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: > 10 would *not* do the trick: You are right. I guess something like issue2844-1.diff will be necessary. I am not sure it is worth the trouble, though. Maybe just change -909 to -MAX_INT? Jakub, how did you discover th

[issue2844] int() lies about base parameter

2008-05-13 Thread Alexander Belopolsky
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10317/issue2844-1.diff __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2844] int() lies about base parameter

2008-05-13 Thread Alexander Belopolsky
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10318/issue2844-1.diff __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2844] int() lies about base parameter

2008-05-13 Thread Alexander Belopolsky
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10319/issue2844-1.diff __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2844] int() lies about base parameter

2008-05-13 Thread Alexander Belopolsky
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10318/issue2844-1.diff __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2845] shutil.copy2() copies permission bits

2008-05-14 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: This seems to be a documentation issue. """ shutil.copy2(src, dst) Similar to copy(), but last access time and last modification time are copied as well. This is similar to the Unix command cp -p. ""

[issue2845] shutil.copy2() copies permission bits

2008-05-14 Thread Alexander Belopolsky
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: -- assignee: -> georg.brandl components: +Documentation -Windows nosy: +georg.brandl type: behavior -> feature request versions: +Python 2.5, Python 2.6, Python 3.0 __ Tracker <[

[issue2863] Generator __name__ and better repr()

2008-05-15 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: Any reason why generator object repr is formed differently from function and code? >>> def f(): yield 1 ... >>> f() >>> f >>> f.__code__ ", line 1> -- nosy: +belopolsky

[issue2869] Wrong doc for `calendar.Calendar.iterweekdays`

2008-05-15 Thread Alexander Belopolsky
Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: -- keywords: +patch Added file: http://bugs.python.org/file10335/issue2869.diff __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2897] include structmember.h in Python.h

2008-05-19 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: Note that structmember.h pollutes global namespace with macros that do not have conventional Py_ or PY_ prefix. READONLY and RESTRICTED macros seem to be most likely to conflict with other code. I would be -0 on inc

[issue2973] _ssl compiler warnings

2008-05-28 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: It looks like this comes from r59493 which purports to fix a warning: r59493 | christian.heimes | 2007-12-13 23:38:13 -0500 (Thu, 13 Dec 2007) | 1 line

[issue3008] Let bin() show floats

2008-05-30 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: I like the idea in general. It is way too common for people to be confused by decimal representation of floats, so an obvious mechanism to display the true value will be helpful. I don't think a promiscuous bin() w

[issue3008] Let bin() show floats

2008-05-30 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: On Fri, May 30, 2008 at 10:52 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: > > Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > > Well it's quite simple. Imagine you have a function f() which t

[issue3008] Let bin() show floats

2008-05-30 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: While writing my previous comments I did not realize that '%x' % accepts floats: >>> "%x" % 3.1415 '3' Float support has been even improved somewhat since 2.5: Python 2.5 (r25:51908, Nov

[issue3008] Let bin() show floats

2008-05-30 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: On Fri, May 30, 2008 at 1:47 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: .. > 2. if two numbers (one integer and one float) are equal, it sounds > expectable that calling a function on them will produce similar

[issue3008] Let bin() show floats

2008-05-30 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: On Fri, May 30, 2008 at 1:47 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: .. > 1. while taking the binary representation of an integer has a real > meaning, taking the binary representation of a float only exposes a

[issue3008] Let bin() show floats

2008-05-30 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: What would you say to adding float-capable bin/oct/hex (+ maybe tobase) to the math module? ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3008] Let bin() show floats

2008-05-30 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: Another problem with bin() on floats is that it will be a one-way street because as far as I know, there is no function to convert a binary string back to a float. My last thought on this issue is that it will be helpful to add

[issue3008] Let bin() show floats

2008-05-30 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: On Fri, May 30, 2008 at 2:32 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: > then why not make it a method of float? .. because you rarely want to make your functions accept 1.0, but reject 1 and using f.bin() in you

[issue3081] Py_(X)SETREF macros

2008-06-13 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: A comment on the patch: Since object.h may be included from C++ extensions, you should not use a C++ keyword "new" as a variable name. -- nosy: +belopolsky ___ Python

[issue2417] [py3k] Integer floor division (//): small int check omitted

2008-07-23 Thread Alexander Belopolsky
Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: It looks like e-mail submission did not work. Uploading updated patch as issue2417b.diff . Added file: http://bugs.python.org/file10962/issue2417b.diff ___ Python tracker <[EMAIL PROTECTE

[issue4331] Can't use _functools.partial() created function as method

2010-01-28 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Christophe, It looks like your patch goes out of its way to avoid creating nested partials. This is a worthwhile goal and I think it should be done in partial_new so that partial(partial(f, x), y) returns partial(f, x, y). If fact, I was surprised to

[issue7830] Flatten nested functools.partial

2010-02-01 Thread Alexander Belopolsky
New submission from Alexander Belopolsky : Currently applying functools.partial to a callable that is already functools.partial object results in a nested object: >>> from functools import partial >>> def f(a,b,c): pass ... >>> p = partial(partial(f, 1),

[issue4331] Can't use _functools.partial() created function as method

2010-02-01 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Please see issue7830 for a related patch. -- ___ Python tracker <http://bugs.python.org/issue4331> ___ ___ Python-bug

[issue7830] Flatten nested functools.partial

2010-02-01 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Antoine> Flattening should only happen for instances of the exact type. I am attaching a variant of the patch that will only flatten if both nested and wrapping partial is of the exact type. Other possibilities would include flattening partial_subt

[issue6877] enable compilation of readline module on Mac OS X 10.5 and 10.6

2010-02-08 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- nosy: +Alexander.Belopolsky ___ Python tracker <http://bugs.python.org/issue6877> ___ ___ Python-bugs-list mailing list Unsub

[issue1726687] Bug found in datetime for Epoch time = -1

2010-02-18 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I wonder: with year bounds being checked in gettmarg() and mktime accepting arbitrary values for the rest of the tm structure members (at least it appears to on my Mac), is it possible trigger "mktime argument out of range"? If it is possib

[issue2736] datetime needs an "epoch" method

2010-02-18 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Victor, As you explain in your own documentation, the proposed method is equivalent to ``(time.mktime(self.timetuple()), self.microsecond)``, so all it does is replacing a less than a one-liner. Moreover, I am not sure time.mktime(self.timetuple

[issue7963] Misleading error message from object(arg)

2010-02-18 Thread Alexander Belopolsky
New submission from Alexander Belopolsky : >>> object(1) Traceback (most recent call last): File "", line 1, in TypeError: object.__new__() takes no parameters This is misleading because object.__new__() takes one parameter: >>> object.__new__(object) I sugg

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-20 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Michael, Can you post the output of "groups" and "id" command from your Mac? It looks like posix_getgroups cannot handle more than NGROUPS_MAX groups and NGROUPS_MAX is 16 on Mac OS. -- nosy: +

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-20 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I was able to reproduce the error. First, add your user name to multiple test groups as follows: $ sudo dscl . -create /Groups/testN GroupMembership username (repeat 16 times with different Ns) $ ./python.exe Python 2.7a3+ (trunk:78265M, Feb 20 2010

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-20 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I am submitting a fix. I am using the following feature documented in getgroups(2): """ If _DARWIN_C_SOURCE is defined, getgroups() can return more than {NGROUPS_MAX} groups. """ It appears that _DARWIN_C_SOURCE is

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-20 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: It looks like the current implementation is not POSIX compliant because it assumes that NGROUPS_MAX is compile time constant. However, according to <http://www.opengroup.org/onlinepubs/95399/functions/getgroups.html>, "Application wri

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-20 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: It looks like the current implementation is not POSIX compliant because it assumes that NGROUPS_MAX is compile time constant. However, according to <http://www.opengroup.org/onlinepubs/95399/functions/getgroups.html>, "Application wri

[issue6280] calendar.timegm() belongs in time module, next to time.gmtime()

2010-02-20 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Francesco, You have my +1 for implementing both 1 and 2 below. """ 1. Use timegm(3) function where HAVE_TIMEGM is defined (i have a working patch for it) 2. Implement a more portable timegm function with tzset and mktime where

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-21 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Sun, Feb 21, 2010 at 1:58 PM, Martin v. Löwis wrote: .. > I would propose a different strategy: if _SC_NGROUPS_MAX is defined, use > that to find out how much memory to allocate, otherwise, fall back to > the current max array size. Can you

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-22 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Here is another interesting fact: Mac OS 10.6 comes with python 2.5 and 2.6 preinstalled: $ python2.5 -V Python 2.5.3c1 $ python2.6 -V Python 2.6.1 Neither of these exhibit the same bug, but both are broken in some way. Given $ cat tg.py import os g

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-22 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Apparently, Apple patches posix_[gs]etgroups functions as follows: for 2.5: http://www.opensource.apple.com/source/python/python-44/2.5/fix/posixmodule.c.ed for 2.6: http://www.opensource.apple.com/source/python/python-44/2.6/fix/posixmodule.c.ed

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-22 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I've converted apple patches to unified diffs, but I cannot reproduce 2.5 behavior. -- Added file: http://bugs.python.org/file16309/apple-2.5-fix-posixmodule.c.diff ___ Python tracker <http://bugs.py

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-22 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: After some head-scratching, I figured out how to reproduce stock python2.5 behavior. It turns out that defining _DARWIN_C_SOURCE not only allows getgroups() output to exceed NGROUPS_MAX (as documented), but also effectively disables setgroups() which

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-22 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I am reclassifying this as a crash because os.getgroups() crashes the interpreter when python is running as root on an unmodified system: $ sudo ./python.exe -c "import os; os.getgroups()" Traceback (most recent call last): File &quo

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Tue, Feb 23, 2010 at 2:20 AM, Ronald Oussoren wrote: > .. > Alexander:  What makes you think r63955 introduced the problem? That revision introduced _DARWIN_C_SOURCE which, as I explained, has two effects on get/setgroups: ""&qu

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Ronald, Have you tested your patch with issue7900-tests.diff? On my system: $ ./python.exe Lib/test/test_posix.py testNoArgFunctions (__main__.PosixTester) ... Segmentation fault and $ sudo ./python.exe Lib/test/test_posix.py .. FAIL

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Tue, Feb 23, 2010 at 8:46 AM, Ronald Oussoren wrote: .. > What I did notice though is that the tests don't actually test the issue at > hand: > having more than 16 secondairy groups on OSX. This is easy to fix: just add another e

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Tue, Feb 23, 2010 at 8:46 AM, Ronald Oussoren wrote: > .. > I get test failures, but no crashes, when I do run the additional tests. The crash that I see is apparently due to underallocated memory: alt_grouplist = PyMem_Malloc(n); sho

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: E-mail to tracker handling still seems to remove '>' quoted lines. I am reposting a couple of comments that got clobbered: -- > * allocate an array of groupcount gid_t's and call getgroups(groupcount) > This is more or less wh

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I think I finally understand what is going on and ready to make what I believe is a reasonable proposal. Setting _DARWIN_C_SOURCE (or _DARWIN_UNLIMITED_GETGROUPS) replaces getgroups with a Darwin extension, but does not change setgroups: $ nm tg1

[issue6280] calendar.timegm() belongs in time module, next to time.gmtime()

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: The patch (I reviewed timemodule-gmtime-trunk.diff) looks mostly correct. One problem that I see is that it will likely produce compiler warnings on the systems without timegm and mktime. The warnings will be due to unused static function time_timegm

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Tue, Feb 23, 2010 at 12:16 PM, Ronald Oussoren wrote: .. > How did you detect that the modern getgroups implementation doesn't > query the kernel? That would be very odd. I wish I could say that I mastered dtrace under OSX, but I am no

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: David, Can you unset "normal" priority from this issue. Regardless of whether it is a crash or not a crash, this is a regression for which there is no user work-around. It looks like "normal" priority makes the issue disappear fr

[issue7736] os.listdir hangs since opendir() and closedir() do not release GIL

2010-02-23 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Another "+1" on the patch if it is needed. Posix module consistently releases the GIL while making system calls and this is a good idea independent of this particular issue. Looking at the patch made me wonder whethe

[issue6280] calendar.timegm() belongs in time module, next to time.gmtime()

2010-02-24 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Looks good. A documentation typo: gmtime() -- convert seconds since Epoch to UTC tuple\n\ +timegm() - Convert a UTC tuple to seconds since the Epoch.\n\ Note the use of -- in the existing items. I understand that the choice of float for return value

[issue8013] time.asctime segfaults when given a time in the far future

2010-02-24 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Looks like a case of missing null check. Patch attached. -- keywords: +patch nosy: +Alexander.Belopolsky Added file: http://bugs.python.org/file16359/issue8013.diff ___ Python tracker <http://bugs.python.

[issue7900] posix.getgroups() failure on Mac OS X

2010-02-24 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Wed, Feb 24, 2010 at 12:45 PM, Martin v. Löwis wrote: .. > I still think that the sysconf version should be the correct one. If OSX > fails to work correctly under > that version, and causes Python to raise an exception - then that's

[issue7150] datetime operations spanning MINYEAR give bad results

2010-02-25 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Given assert(*m > 0); assert(*d > 0); at the end of normalize_y_m_d(), it looks like at lest 1 <=*month and 1 <=*day are redundant. A closer look also reveals assert(1 <= *m && *m <= 12); in the

[issue7150] datetime operations spanning MINYEAR give bad results

2010-02-25 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Aha! My reliance on asserts() was misguided. With the debug build: >>> t0-d2 Assertion failed: (ordinal >= 1), function ord_to_ymd, file /Users/sasha/Work/python-svn/trunk/Modules/datetimemodule.c, line 269. Abort trap Should we reclass

[issue8015] pdb "commands" command throws you into postmortem if you enter an empty command

2010-02-25 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I am attaching the patch that fixes the issue by ignoring empty and all space lines during commands' entry. Note that as written the patch also makes pdb ignore shell escapes unless it is extended with do_shell method. I think this is the

[issue7999] setregid does not work with -1 as argument

2010-02-25 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I reproduced this bug on OSX 10.6: >>> os.setregid(-1,-1) Traceback (most recent call last): File "", line 1, in OverflowError: group id too big Since -1 has special meaning as an argument to POSIX setregid(rgid, egid), "&q

[issue887237] Machine integers

2010-03-04 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I would like to hear from Thomas before introducing macros in this code. I tried to follow the style of cfield.c which shows similar code duplication. There are also some questions that need to be answered before polishing the code. 1. Should mixed

[issue8065] Memory leak in readline.get_current_history_length

2010-03-05 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Note the following comment elsewhere in Modules/readline.c: /* the history docs don't say so, but the address of state changes each

[issue8065] Memory leak in readline.get_current_history_length

2010-03-05 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Not directly related to the issue at hand, but I've noticed that while readline.get_current_history_length() is tested in the unittests, readline.get_history_length() is not. Attached patch adds tests for reading and writing history files. Al

[issue887237] Machine integers

2010-03-05 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Attaching a patch that is equivalent toissue887237.diff, but uses preprocessor to generate repetitive code. -- Added file: http://bugs.python.org/file16466/issue887237-macro.diff ___ Python tracker <h

[issue6953] readline documenation needs work

2010-03-06 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- nosy: +Alexander.Belopolsky ___ Python tracker <http://bugs.python.org/issue6953> ___ ___ Python-bugs-list mailing list Unsub

[issue8065] Memory leak in readline.get_current_history_length

2010-03-06 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: It appears that the tests that I attached fail when libedit is used. This is clearly due to bugs in libedits readline emulation: 1. read_history does not update history_length 2. history_truncate_file does not preserver the history cookie

[issue6953] readline documenation needs work

2010-03-09 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Tue, Mar 9, 2010 at 4:24 PM, stefanholek wrote: .. > To be zero-based, get_history_item would need to look like: .. > +       if ((hist_ent = history_get(history_base + idx))) Did you test this with l

[issue8065] Memory leak in readline.get_current_history_length

2010-03-09 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I my experience, reporting bugs in open source components of OSX to bugreport.apple.com is a waste of time. Such reports are largely ignored and they are not visible to upstream developers. I believe the upstream for libedit is NetBSD, http

[issue8065] Memory leak in readline.get_current_history_length

2010-03-09 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I submitted two bug reports: 7734961 libedit history_truncate_file () fails to preserve magic line Mac OS X Other Bug 09-Mar-2010 05:48 PM Open 7734839 libedit read_history() does not update history_length Mac OS X Other Bug 09-Mar-2010 05:39 PM Open

[issue4376] Nested ctypes 'BigEndianStructure' fails

2010-03-11 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: theller> - Should 'part' be inserted as is, [possibly] leading theller> to a total structure of fields with mixed byte order? +1 for this option. -- nosy: +Alexander.Belopolsky ___ Pytho

[issue8154] os.execlp('true') crashes the interpreter on 2.x

2010-03-16 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: As far as I can tell, it does not *crash* the interpreter. Instead, it replaces the python interpreter process with a "true" utility. $ ./python.exe Python 2.7a4+ (trunk:78816M, Mar 9 2010, 18:57:13) [GCC 4.2.1 (Apple Inc. build 5646) (

[issue8154] os.execlp('true') crashes the interpreter on 2.x

2010-03-16 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I forgot to add that this behavior is documented: os.execlp = execlp(file, *args) execlp(file, *args) Execute the executable file (which is searched for along $PATH) with argument list args, replacing the current process

[issue8154] os.execlp('true') crashes the interpreter on 2.x

2010-03-16 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: The original report, issue1039 has a better problem description: "In a windows debug build, an assertion is triggered when os.execvpe is called with an empty argument list: self.assertRaises(OSError, os.execvpe, 'no such app-', [], No

[issue8154] os.execlp('true') crashes the interpreter on 2.x

2010-03-16 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Adding Thomas. Thomas, Do you remember why your patch for issue1039 was not backported? -- nosy: +theller ___ Python tracker <http://bugs.python.org/issue8

[issue8154] os.execlp('true') crashes the interpreter on 2.x

2010-03-16 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Tue, Mar 16, 2010 at 7:46 PM, Matthias Klose wrote: .. > it does crash: Strange. Can you report your Linux version and the stack trace from the crash? On Ubuntu, 2.6.24-27-generic #1 SMP Wed Jan 27 23:54:28 UTC 2010 i686 GNU/Linux, I see no cr

[issue8154] os.execlp('true') crashes the interpreter on 2.x

2010-03-18 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Thu, Mar 18, 2010 at 3:32 PM, R. David Murray wrote: .. > I agree that this should be fixed, since we presumably want to be "strictly > conforming" to the posix standards, > but it looks like this is a regression in either linux

[issue3135] inspect.getcallargs()

2010-03-18 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- nosy: +Alexander.Belopolsky ___ Python tracker <http://bugs.python.org/issue3135> ___ ___ Python-bugs-list mailing list Unsub

[issue6474] Inconsistent TypeError message on function calls with wrong number of arguments

2010-03-18 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- nosy: +Alexander.Belopolsky ___ Python tracker <http://bugs.python.org/issue6474> ___ ___ Python-bugs-list mailing list Unsub

[issue8174] Misleading reported number of given arguments on function call TypeError

2010-03-18 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- nosy: +Alexander.Belopolsky ___ Python tracker <http://bugs.python.org/issue8174> ___ ___ Python-bugs-list mailing list Unsub

[issue3690] sys.getsizeof wrong for Py3k bool objects

2010-03-18 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- nosy: +Alexander.Belopolsky ___ Python tracker <http://bugs.python.org/issue3690> ___ ___ Python-bugs-list mailing list Unsub

[issue8191] Make arg0 required argument in os.execl* functions

2010-03-21 Thread Alexander Belopolsky
New submission from Alexander Belopolsky : Since issue1039 made it illegal to pass empty argument list to execv*, I suggest to change signature of os.execl* functions and make arg0 a required positional argument. This is not a backward compatible change because os.execlp('true&#x

[issue8154] os.execlp('true') crashes the interpreter on 2.x

2010-03-21 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Please see related issue8191. -- ___ Python tracker <http://bugs.python.org/issue8154> ___ ___ Python-bugs-list mailin

[issue1039] Asssertion in Windows debug build

2010-03-21 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Link to revision: r57731 -- nosy: +Alexander.Belopolsky ___ Python tracker <http://bugs.python.org/issue1039> ___ ___

[issue1039] Asssertion in Windows debug build

2010-03-21 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: This issue was misclassified as an interpreter crash while in fact it was a bug in the underlying OS utility. Please see discussion in issue8154. Since the fix changes behavior, it should be documented and a NEWS entry added. -- type: crash

[issue8191] Make arg0 required argument in os.execl* functions

2010-03-21 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Sun, Mar 21, 2010 at 2:52 PM, Matthias Klose wrote: .. > os.execlp('true') does raise ValueError on released 3.x versions. sorry if I > do misunderstand something. My bad. I thought it was a more recent change. However as far as I

[issue8176] Interpreter crash with "double free or corruption" message

2010-03-21 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Clearly not enough information, but I have a few observations: 1. Clearly the crash occurs on exit (in Py_Finalize) during a module cleanup. (Unfortunately it looks like a non-debug build of Python was used so figuring out which module is involved may

[issue8026] strftime bug when timedelta is negative

2010-04-12 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: This is not a bug. The issue boils down to the following: >>> from datetime import * >>> d = datetime(2010, 1, 1) >>> d, d.strftime("%G") (datetime.datetime(2010, 1, 1, 0, 0), '2009') and OP expects '

[issue2706] datetime: define division timedelta/timedelta

2010-04-12 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Is there a good reason why this issue is languishing? The requested functionality seems to be well motivated, simple to implement with few objections resolved in the discussion. I wonder if it would be helpful to limit this patch to 3.x series. That

[issue8191] Make arg0 required argument in os.execl* functions

2010-04-19 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Google code search for os.execlp\([^*,]+\) lang:python returns 15 hits, two of which are the same as Matthias found. I am not sure what these results mean for the issue (and Matthias does not reach a conclusion either.) Note that the status quo in 3

[issue8154] os.execlp('true') crashes the interpreter on 2.x

2010-04-19 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: If this new feature stays in 3.x, shouldn't 2.7 have a -3 warning? Also, I would consider adding os.execlp(path) -> os.execlp(path, os.path.basename(path)) transformation to 2to3. -- ___ Python

[issue8154] os.execlp('true') crashes the interpreter on 2.x

2010-04-19 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I noticed that the change is still present in 2.7a. For what it's worth, I agree with David: """ Since it does trigger a crash on the windows equivalent API, the check should be conditional on platform. And it should generate a p

[issue2706] datetime: define division timedelta/timedelta

2010-04-19 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I am attaching a forward port of Victor's timedelta_true_divide_divmod.patch to py3k. -- nosy: +Alexander.Belopolsky Added file: http://bugs.python.org/file16990/issue2706.diff ___ Python tracker

[issue2706] datetime: define division timedelta/timedelta

2010-04-19 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- nosy: -belopolsky ___ Python tracker <http://bugs.python.org/issue2706> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue2706] datetime: define division timedelta/timedelta

2010-04-19 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On Mon, Apr 19, 2010 at 4:09 PM, Mark Dickinson wrote: I noticed that as I was porting Victor's patch. I did not add timedelta % timedelta because I found out that timedelta % int is not supported in the released versions while timedelta // int i

[issue2706] datetime: define division timedelta/timedelta

2010-04-19 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: I should be able to add timedelta % timedelta and fix the nits that Mark mentioned tonight. -- ___ Python tracker <http://bugs.python.org/issue2

[issue2706] datetime: define division timedelta/timedelta

2010-04-19 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: New patch, issue2706a.diff, implements timedelta % timedelta and addresses Mark's code review comments. With respect to Mark's """ One other thought: with this division operation added, it might be nice to add constants lik

[issue2706] datetime: define division timedelta/timedelta

2010-04-19 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : Removed file: http://bugs.python.org/file16990/issue2706.diff ___ Python tracker <http://bugs.python.org/issue2706> ___ ___ Python-bug

<    6   7   8   9   10   11   12   13   14   15   >