[issue39729] stat.S_ISXXX can raise OverflowError for remote file modes
Arnon Yaari added the comment: Maybe so, but IMHO it is a lesser concern - the operating systems that use "unsigned long" add bits on the right, and don't change the less significant bits that the S_ISXXX macros check (if I am not mistaken, those bits are POSIX standards). This issue is a regression from Python 2.7, so I believe it should be addressed. -- ___ Python tracker <https://bugs.python.org/issue39729> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39729] stat.S_ISXXX can raise OverflowError for remote file modes
New submission from Arnon Yaari : The C implementation of the "stat" module on Python 3 (_stat) is using the type "mode_t" for file modes, which differs between operating systems. This type can be defined as either "unsigned short" (for example, in macOS, or the definition added specifically for Windows in _stat.c) or "unsigned long" (Linux and other Unix systems such as AIX). This means that the "stat" module may only work with file modes that come from the same system that Python was compiled for. It is sometimes desirable to work with file modes on remote systems (for example, when using the "fabric" module to handle remote files - https://github.com/fabric/fabric/blob/1.10/fabric/sftp.py#L42). With the pure-python "stat" module on Python 2.7, using macros such as "stat.S_ISDIR" with any value used to work (even values that exceed "unsigned short" on macOS, for example) but with the C implementation this can result in an exception on systems with an "unsigned short" mode_t: >>> stat.S_ISDIR(0o240755) OverflowError: mode out of range I encountered this exception when trying to "put" files from a macOS system to an AIX system with "fabric" (0o240755 is the st_mode found for "/" on AIX). For uniform handling of file modes, modes should be handled as unsigned long instead of the system-defined "mode_t". -- components: Library (Lib) messages: 362499 nosy: wiggin15 priority: normal severity: normal status: open title: stat.S_ISXXX can raise OverflowError for remote file modes type: behavior versions: Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue39729> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38527] configure script fails to detect "float word ordering" on Solaris
Change by Arnon Yaari : -- keywords: +patch pull_requests: +16395 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16845 ___ Python tracker <https://bugs.python.org/issue38527> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38527] configure script fails to detect "float word ordering" on Solaris
New submission from Arnon Yaari : When running the configure script on Solaris SPARC (versions 10 and 11), the script fails with the following error: checking whether float word ordering is bigendian... unknown configure: error: Unknown float word ordering. You need to manually preset ax_cv_c_float_words_bigendian=no (or yes) according to your system. The configure script uses "grep" on a compiled binary to see how a float variable is compiled. On Solaris, the regular "grep" command may be an old version that fails to search in a binary file. The correct command should be "ggrep" (the GNU grep). Luckily, Python's configure script already finds this command in an earlier check: checking for grep that handles long lines and -e... /usr/bin/ggrep All we have to do, then, is use the command that configure finds. i.e. replace "grep" -> "$GREP". -- components: Build messages: 354941 nosy: wiggin15 priority: normal severity: normal status: open title: configure script fails to detect "float word ordering" on Solaris versions: Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue38527> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28373] input() prints to original stdout even if sys.stdout is wrapped
New submission from Arnon Yaari:
When I wrap sys.stdout with a custom object that overrides the 'write' method,
regular prints use the custom write method, but the input() function prints the
prompt to the original stdout.
This is broken on Python 3.5. Earlier versions work correctly.
In the following example 'write' does nothing, so I expect no output, but the
input() function outputs to stdout anyway:
import sys
class StreamWrapper(object):
def __init__(self, wrapped):
self.__wrapped = wrapped
def __getattr__(self, name):
# 'write' is overridden but for every other function, like 'flush', use
the original wrapped stream
return getattr(self.__wrapped, name)
def write(self, text):
pass
orig_stdout = sys.stdout
sys.stdout = StreamWrapper(orig_stdout)
print('a') # this prints nothing
input('b') # this should print nothing, but prints 'b' (in Python 3.5 and up
only)
Looks like this was broken in http://bugs.python.org/issue24402 . Adding the
'fileno' function from this issue fixes the problem, but it's just a
workaround. This affects the colorama package:
https://github.com/tartley/colorama/issues/103
--
messages: 278179
nosy: wiggin15
priority: normal
severity: normal
status: open
title: input() prints to original stdout even if sys.stdout is wrapped
versions: Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28373>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11215] test_fileio error on AIX
Arnon Yaari added the comment: Some AIX systems have seekable /dev/tty, as is the case here and in msg90762, and on my system too. There is already an exemption in test_fileio.py for systems that have a seekable /dev/tty. AIX just needs to be exempt too. (from my experience, AIX and Solaris behave similarly in many cases, so it makes sense to add aix next to sunos). I'm submitting a patch to fix this test case on AIX. -- keywords: +patch nosy: +wiggin15 Added file: http://bugs.python.org/file40622/issue11215.diff ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11215> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue19006] UnitTest docs should have a single list of assertions
Changes by Arnon Yaari <wiggi...@gmail.com>: -- nosy: +wiggin15 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19006> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue678264] test_resource fails when file size is limited
Arnon Yaari added the comment: This issue is still relevant and can be reproduced by running: ulimit -Hf 1000 ./python Lib/test/test_resource.py (On AIX, the default hard limit is not RLIM_INFINITY so it reproduces on that operating system without the first line) The patch is still relevant and fixes the issue. It looks like it's doing the right thing, but it can't be committed until #9917 will be fixed - otherwise the tests will break on Linux, where RLIM_INFINITY is -1 and not greater than 0. -- nosy: +wiggin15 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue678264> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9917] resource max value represented as signed when should be unsigned
Arnon Yaari added the comment: I'm submitting a patch for review. I tested this and verified the values on Redhat and Unbuntu (both x86 and x64), Mac OS X (x64) and AIX (32-bit process on ppc64). 'configure' and 'pyconfig.h.in' were auto-generated with autoconf and autoheader, respectively. A test for this patch (along with a fix for a different test failure) is in msg117130 -- keywords: +patch Added file: http://bugs.python.org/file40613/issue9917.diff ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9917> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9917] resource max value represented as signed when should be unsigned
Arnon Yaari added the comment: getrlimit still returns -1 as 'max' when limit is unlimited and for RLIM_INFINITY because rlim_t is considered signed. The zshell project decides whether rlim_t is signed/unsigned (and also whether it is long or long long) in the configure step: https://github.com/zsh-users/zsh/blob/8b84419f45298ee564bd6fa2b531c8991b2a1983/configure.ac#L1859 On Linux, rlim_t is unisnged long long so the conversion should be done using PyLong_FromUnsignedLongLong (for RLIM_INFINITY) and using 'KK' instead of 'LL' in 'rlimit2py'. IMHO the best way to fix this is to add configure steps like in zsh and then adding ifdefs to resource.c - in rlimit2py and near PyModule_AddObject of RLIM_INFINITY -- nosy: +wiggin15 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9917> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24886] open fails randomly on AIX
New submission from Arnon Yaari: We are using Python 2.7.8 on AIX 7.1 TL 3. On rare occasions, calls to open files with mode w fail with: IOError: File exists. File /root/jenkins/workspace/powertools/eggs/infi.credentials_store-0.1-py2.7.egg/infi/credentials_store/base.py, line 175, in set_credentials with open(self.get_file_path(), 'w') as f: IOError: [Errno 17] File exists: '/root/.infinidat/infinihost' This happens randomly on multiple systems and different files (including e.g. /dev/null). This is very strange because File exists should only be raised if we open the file with the 'x' flag (os.O_EXCL) and we don't. After debugging, we discovered that this happens due to a bug in AIX. On AIX, fopen checks for mode[2] (where 'mode' is the second argument passed to it - in our case, w) regardless of its length. fopen checks this byte against 'x' to decide if O_EXCL should be used. In the case of passing w as 'mode', mode[2] will contain undefined data -- and in rare cases it will contain the byte 'x'. This was reported to IBM and APARs exist for this issue: http://www.ibm.com/support/docview.wss?uid=isg1IV64453 (see related APARs for various AIX versions in this page) Python can and should work around this because the code in fileobject.c is also partly to blame: Python 2.7.x contains the following lines: /* probably need to replace 'U' by 'rb' */ newmode = PyMem_MALLOC(strlen(mode) + 3); For the 'mode' parameter, Python allocates 3 additional bytes that are not always used, and these bytes contain uninitialized data. The byte 'x' that causes the problem comes from this allocation. Python should set the bytes to zero to avoid this issue. I'm attaching a patch. Note that this applies only to the 2.x branch. -- files: aix_fopen_fix.diff keywords: patch messages: 248769 nosy: wiggin15 priority: normal severity: normal status: open title: open fails randomly on AIX versions: Python 2.7 Added file: http://bugs.python.org/file40202/aix_fopen_fix.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24886 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20523] global .pdbrc on windows 7 not reachable out of the box
Changes by Arnon Yaari wiggi...@gmail.com: -- nosy: +wiggin15 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20523 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20362] longMessage attribute is ignored in unittest.TestCase.assertRegexpMatches etc
Arnon Yaari added the comment: * The removal of the 'kot' test is ok. That's what the fix is about. With longMessage set to False, we should only see the custom message, 'Message', and not the message about the regex that contains 'kot'. * Please update the patch for 3.5 to use assertRegex and assertNotRegex in the assertMessages call. These are the new names. With the current patch, the tests throw deprecation warnings. Other than that the patch looks good (I am not a committer, though, so I can't help further). -- versions: -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20362 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12485] textwrap.wrap: new argument for more pleasing output
Changes by Arnon Yaari wiggi...@gmail.com: -- nosy: +wiggin15 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12485 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20362] longMessage attribute is ignored in unittest.TestCase.assertRegexpMatches etc
Changes by Arnon Yaari wiggi...@gmail.com: -- nosy: +wiggin15 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20362 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20769] Reload() description is unclear
Changes by Arnon Yaari wiggi...@gmail.com: -- nosy: +wiggin15 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20769 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method (also for bytearray and memoryview)
Arnon Yaari added the comment: minor updates to stdtypes.rst. I also want to add a line to whatsnew/3.5 but don't know how to put it in words - maybe it's better if someone with better english will add it. -- Added file: http://bugs.python.org/file39204/bytes.hex-1.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13866] {urllib, urllib.parse}.urlencode should not use quote_plus
Changes by Arnon Yaari wiggi...@gmail.com: Removed file: http://bugs.python.org/file39006/issue13866.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13866 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23949] Number of elements display in error message is wrong while unpacking in traceback
Changes by Arnon Yaari wiggi...@gmail.com: Removed file: http://bugs.python.org/file39011/issue23949.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23949 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13866] {urllib, urllib.parse}.urlencode should not use quote_plus
Arnon Yaari added the comment: Fixed Martin's comments. -- Added file: http://bugs.python.org/file39036/issue13866.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13866 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4254] _cursesmodule.c callable update_lines_cols()
Arnon Yaari added the comment: Fixed David's comments -- versions: +Python 3.5 -Python 3.2 Added file: http://bugs.python.org/file39037/issue4254.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4254 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4254] _cursesmodule.c callable update_lines_cols()
Changes by Arnon Yaari wiggi...@gmail.com: Removed file: http://bugs.python.org/file38973/patch_4254.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4254 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23949] Number of elements display in error message is wrong while unpacking in traceback
Arnon Yaari added the comment: I couldn't find a way to add 'got %d' to the 'too many values' message. This would either require going over the rest of the iterator (which will take more time and may never return) or trying to figure out if it has a 'len' member. I didn't find any place in the current code that does something like this and writing one myself is too error prone (there are so many cases...). PyObject_Size returns an error if I try to use it for this purpose. I found another message with need more than ... that I improved in the same way. This message is for when trying to execute: a, *(b, c, d) = 1, (2, 3), (4, 5) Now it outputs the message for the star unpacking: ValueError: not enough values to unpack (expected 3, got 2) which is confusing in this use case but still better than before. Oh my! -- Added file: http://bugs.python.org/file39039/issue23949.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23949 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23949] Number of elements display in error message is wrong while unpacking in traceback
Changes by Arnon Yaari wiggi...@gmail.com: Added file: http://bugs.python.org/file39042/issue23949-2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23949 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23949] Number of elements display in error message is wrong while unpacking in traceback
Arnon Yaari added the comment: I fixed the tests (that's important!) and changed the latter message to specify it is referring to the starred target (the term starred target appears in the docs in simple_stmts.rst). Looks like the number in that message was wrong before! The test looked like this: a, *b, c, d, e = 0, 1, 2 ValueError: need more than 3 values to unpack Need more than 3? Not exactly. The new message looks like this: a, *b, c, d, e = 0, 1, 2 ValueError: not enough values to unpack into starred target (expected at least 4, got 3) -- Added file: http://bugs.python.org/file39041/issue23949-1.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23949 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4254] _cursesmodule.c callable update_lines_cols()
Arnon Yaari added the comment: I'm adding patch without the update to Misc/NEWS. I'm not sure why, but the curses doc refers to LINES and COLS as environment variables. In the doc change I referred to them as just variables and used the notation that works for linking to them, using :envvar: -- Added file: http://bugs.python.org/file39044/issue4254-1.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4254 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23949] Number of elements display in error message is wrong while unpacking in traceback
Changes by Arnon Yaari wiggi...@gmail.com: Added file: http://bugs.python.org/file39043/issue23949-3.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23949 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23949] Number of elements display in error message is wrong while unpacking in traceback
Arnon Yaari added the comment: Sorry, I got confused (which proves the point of the ticket :)) * the need more than 3 values error message wasn't wrong, just confusing. * Including into starred target in the message was incorrect, I removed it. * The message with expected at least ... (when there is a star target) didn't show if there weren't enough values to fill the arguments before the star argument. I fixed this now too and added a test. -- Added file: http://bugs.python.org/file39046/issue23949-4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23949 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4254] _cursesmodule.c callable update_lines_cols()
Arnon Yaari added the comment: Adding a test that only calls the function. -- Added file: http://bugs.python.org/file39048/issue4254-2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4254 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15625] Support u and w codes in memoryview
Arnon Yaari added the comment: The documentation already specifies that 'u' is deprecated and doesn't mention the 'w' code. I think we can close this issue. -- nosy: +wiggin15 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15625 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9014] Incorrect documentation of the PyObject_HEAD macro
Arnon Yaari added the comment: PEP 3123 is the one that describes this change. I'm submitting a file with the proposed changes to the docs. -- keywords: +patch nosy: +wiggin15 Added file: http://bugs.python.org/file38991/issue9014.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9014 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13866] {urllib, urllib.parse}.urlencode should not use quote_plus
Arnon Yaari added the comment: Updated patch to the correct format, added a test and some more documentation. -- nosy: +wiggin15 versions: +Python 3.5 -Python 3.4 Added file: http://bugs.python.org/file39006/issue13866.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13866 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23949] Number of elements display in error message is wrong while unpacking in traceback
Arnon Yaari added the comment: Adding alternative patch for suggestion. -- nosy: +wiggin15 versions: +Python 3.5 -Python 3.2 Added file: http://bugs.python.org/file39011/issue23949.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23949 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method (also for bytearray and memoryview)
Changes by Arnon Yaari wiggi...@gmail.com: Removed file: http://bugs.python.org/file19175/bytes.hex.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method (also for bytearray and memoryview)
Arnon Yaari added the comment: I added the implementation for memoryview, updated to use PyUnicode_New etc., and moved the common implementation to its own file for code reuse. -- Added file: http://bugs.python.org/file38947/bytes.hex.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method (also for bytearray and memoryview)
Changes by Arnon Yaari wiggi...@gmail.com: Added file: http://bugs.python.org/file38961/bytes.hex.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method (also for bytearray and memoryview)
Changes by Arnon Yaari wiggi...@gmail.com: Removed file: http://bugs.python.org/file38947/bytes.hex.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4254] _cursesmodule.c callable update_lines_cols()
Arnon Yaari added the comment: Creating an automatic test for this issue proves difficult, as using curses to resize the terminal already updates the values, and using ioctls to try to bypass curses, doesn't work. I'm adding a manual test program (mostly taken from http://www.gossamer-threads.com/lists/python/python/226137), and a newer patch with documentation. -- nosy: +wiggin15 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4254 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4254] _cursesmodule.c callable update_lines_cols()
Changes by Arnon Yaari wiggi...@gmail.com: Added file: http://bugs.python.org/file38971/manual_test_4254.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4254 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4254] _cursesmodule.c callable update_lines_cols()
Changes by Arnon Yaari wiggi...@gmail.com: Added file: http://bugs.python.org/file38973/patch_4254.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4254 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method (also for bytearray and memoryview)
Changes by Arnon Yaari wiggi...@gmail.com: -- nosy: +eric.smith ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16050] ctypes: callback from C++ to Python fails with Illegal Instruction call
Arnon Yaari added the comment: libffi seem to have fixed this issue in their commit 4acf005 - Build fix for soft-float power targets. The fix is different than what Pavel suggested, but sounds like it should do the same. -- nosy: +wiggin15 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16050 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method
Arnon Yaari added the comment:
You can follow the discussion I linked in the ticket description for an answer:
http://psf.upfronthosting.co.za/roundup/tracker/issue3532
Mainly the answer is: to conform to PEP 358 and to provide the opposite of
bytes.fromhex.
I agree that you can use binascii, but apparently it was decided that this
functionality is good to have in the builtins (what used to be
encode/decode('hex') in Python 2.x, and what is now bytes.fromhex, with the
missing bytes.hex). In addition, binascii works a little differently - already
discussed in the given link...
--
status: pending - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9951
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method
Arnon Yaari added the comment: Hi, is there any chance to get this merged? This ticket has been open for almost 3 years... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method
Changes by Arnon Yaari wiggi...@gmail.com: Added file: http://bugs.python.org/file19175/bytes.hex.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method
Changes by Arnon Yaari wiggi...@gmail.com: Removed file: http://bugs.python.org/file19018/bytes.hex.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method
Arnon Yaari wiggi...@gmail.com added the comment: fixed to Py_UNICODE -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9996] binascii should convert unicode strings
New submission from Arnon Yaari wiggi...@gmail.com: binascii is currently bytes-only, although the a in a2b\b2a should refer to unicode strings. This patch fixes all a2b functions to take str type and all b2a functions to return str types. This was discussed several times, for example: http://www.gossamer-threads.com/lists/python/dev/863892 http://bugs.python.org/issue4770#msg78475 As discussed, the required behavior in Python 3k is that a2b should convert str to bytes and vice versa, and this was implemented in this patch. This patch breaks backward compatibility in several functions... It also required fixing several files under Lib (although most cases were simplified), and also to change the interface of the base64 and quopri modules (this was also requested, e.g. http://bugs.python.org/issue4769). Note that there already was a small change in this behavior from 3.1 to 3.2 (http://bugs.python.org/issue4770) - b2a_hex and b2a_qp COULD receive strings as input in 3.1 and this was changed in 3.2, so technically, compatibility was already broken... The patch includes updates to the standard library, the tests and documentation. rlecode and rledecode were left untouched because they are not a2b\b2a functions per se - they work on the input and output of the hqx functions (maybe it's a good idea to add new a2b\b2a functions for rle_hqx). Any thoughts are welcome. -- components: Interpreter Core files: binascii.diff keywords: patch messages: 117727 nosy: wiggin15 priority: normal severity: normal status: open title: binascii should convert unicode strings type: behavior versions: Python 3.2 Added file: http://bugs.python.org/file19067/binascii.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9996 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9951] introduce bytes.hex method
New submission from Arnon Yaari wiggi...@gmail.com: Following up on these discussions: http://psf.upfronthosting.co.za/roundup/tracker/issue3532 http://www.gossamer-threads.com/lists/python/dev/863892 I'm submitting a patch to add bytes.hex method in accordance to PEP 358. The code was taken from binascii so it should be tested. Also added bytearray.hex and fixed the documentation and testing. There are additional things to discuss, for example: * multiple and different implementations of tohex\fromhex - in binascii, sha1module, bytes, bytearray... * binascii's functions which perform the same thing, but those functions and the rest of binascii's functions receive and return wrong types. I would fix this but it breaks compatibility. -- components: Interpreter Core files: bytes.hex.diff keywords: patch messages: 117397 nosy: wiggin15 priority: normal severity: normal status: open title: introduce bytes.hex method type: feature request versions: Python 3.2 Added file: http://bugs.python.org/file19018/bytes.hex.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9951 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
