[issue1206] logging/__init__.py
New submission from Oleg Broytmann: See the thread in the python-dev mailing list: http://mail.python.org/pipermail/python-dev/2007-September/074732.html -- components: Library (Lib) files: __init__.py.patch messages: 56145 nosy: phd severity: minor status: open title: logging/__init__.py versions: Python 2.5 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1206> __--- __init__.py.orig 2007-04-05 22:11:22.0 +0400 +++ __init__.py 2007-09-26 20:44:59.0 +0400 @@ -223,7 +223,7 @@ # 'Value is %d' instead of 'Value is 0'. # For the use case of passing a dictionary, this should not be a # problem. -if args and (len(args) == 1) and args[0] and (type(args[0]) == types.DictType): +if args and len(args) == 1 and isinstance(args[0], dict) and args[0]: args = args[0] self.args = args self.levelname = getLevelName(level) ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue821862] ftplib: Strict RFC 959 (telnet in command channel)
Oleg Broytmann added the comment:
> Other than IAC what other chars need to be doubled?
Only IAC must be doubled. Also there have to be a special prefix for urgent
(out-of-bound) commands (ABORt); I didn't implement that.
> As an alternative to a brand new TelnetFTP class this can be implemented as a
> FTP class attribute ("strict_telnet" maybe) defaulting to True.
See the first patch. Default value is False to preserve backward compatibility.
--
___
Python tracker
<http://bugs.python.org/issue821862>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2482] Decimal(unicode)
New submission from Oleg Broytmann <[EMAIL PROTECTED]>: Decimal(u'123').to_eng_string() returns unicode in Python 2.5.2. That's probably due to the optimization in decimal module, after which decimal stores coefficient (mantissa) as a str, and doesn't coerce input to str. See the thread at http://mail.python.org/pipermail/python-dev/2008-March/078189.html -- components: Library (Lib) messages: 64488 nosy: phd severity: normal status: open title: Decimal(unicode) type: behavior versions: Python 2.5 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2482> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2666] webbrowser.py doesn't properly handle BROWSER env var
New submission from Oleg Broytmann <[EMAIL PROTECTED]>: webbrowser.py ignores browsers listed in the BROWSER environment variables if it doesn't recognize the browser. For example, if I add "links2" to the BROWSER env var, webbrowser.py ignores it. It is because _synthesize() doesn't know how to handle an unknown browser. The attached patch checks if _synthesize() doesn't register a browser and registers a GenericBrowser. Another approach would be to register GenericBrowser in _synthesize(). -- components: Library (Lib) files: webbrowser.py.patch keywords: patch messages: 65665 nosy: phd severity: normal status: open title: webbrowser.py doesn't properly handle BROWSER env var type: behavior versions: Python 2.5 Added file: http://bugs.python.org/file10072/webbrowser.py.patch __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2666> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2666] webbrowser.py doesn't properly handle BROWSER env var
Oleg Broytmann <[EMAIL PROTECTED]> added the comment: Update the patch. Added file: http://bugs.python.org/file12015/webbrowser.py.patch ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2666> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2666] webbrowser.py doesn't properly handle BROWSER env var
Changes by Oleg Broytmann <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10072/webbrowser.py.patch ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2666> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable
Oleg Broytmann added the comment: I didn't test ifndef-version, I tested the full version (issue6070.patch) on both Linux and w32. You are right, 'mode' must be defined even on w32. -- ___ Python tracker <http://bugs.python.org/issue6070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1576598] ftplib doesn't follow standard
Oleg Broytmann added the comment: This is a duplicate of the issue http://bugs.python.org/issue821862 -- nosy: +phd ___ Python tracker <http://bugs.python.org/issue1576598> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue821862] ftplib: Strict RFC 959 (telnet in command channel)
Oleg Broytmann added the comment: Since I've created the issue I found there are different servers even in Unix. ProFTPd (and, I believe wu-ftpd) strictly implement telnet-in-command channel, they even don't have an option to turn it off. PureFTPd doesn't implement it. On the client side - lftp (command line client) and squid (well-known web/ftp proxy) implement telnet-in-command channel. -- nosy: +ods ___ Python tracker <http://bugs.python.org/issue821862> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6070] Pyhon 2.6 makes .pyc/.pyo bytecode files executable
New submission from Oleg Broytmann : On compilation of .pyc/.pyo bytecode files on import Python 2.6 copies Unix file access attributes (-rwx-) from the imported file. I'd think it's ok except for executable (-x-) bit - bytecode files are not directly executable. That is, for a module.py with attributes -rwxr-x--- I expect python2.6 -c 'import module' would produce module.pyc with attributes -rw-r-. python compileall.py . saves compiled files without the executable bit; it doesn't copy attributes - it just saves files and saving obeys umask. python2.5 -c 'import module.py' doesn't copy the executable bit, it obeys umask too. I consider this as a regression in 2.6. Please mask out executable bits on bytecode files saving. -- components: Interpreter Core messages: 88112 nosy: phd severity: normal status: open title: Pyhon 2.6 makes .pyc/.pyo bytecode files executable type: behavior versions: Python 2.6 ___ Python tracker <http://bugs.python.org/issue6070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6070] Pyhon 2.6 makes .pyc/.pyo bytecode files executable
Oleg Broytmann added the comment: I will try to look at import.c, though I must say I am a bad C programmer. I have switched to Python after ten years of Pascal. Low priority is ok. -- ___ Python tracker <http://bugs.python.org/issue6070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable
Oleg Broytmann added the comment: import_patch2.patch doesn't work for me. I patched and compiled Python 2.6.2 and without installing it ran ./python -c "import test" in the build directory. It copied executable bits from test.py to test.pyc. -- ___ Python tracker <http://bugs.python.org/issue6070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable
Oleg Broytmann added the comment: I am not on Windows. I am on Linux. -- ___ Python tracker <http://bugs.python.org/issue6070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable
Oleg Broytmann added the comment: Sorry, found the bug in my process of testing. ./python uses /usr/lib/python26.so instead of ./python26.so. Setting LD_LIBRARY_PATH=. fixes the problem and the test passes. The patch is ok. -- ___ Python tracker <http://bugs.python.org/issue6070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable
Oleg Broytmann added the comment: I can confirm the patch works on WinXP on NTFS partition and Samba-shared network drive. I have WinXP running in an emulator (VirtualBox) and I compiled Python using MSVC90 Express. -- ___ Python tracker <http://bugs.python.org/issue6070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6070] Python 2.6 makes .pyc/.pyo bytecode files executable
Oleg Broytmann added the comment: Yes, I think #ifndef MS_WINDOWS is enough. -- ___ Python tracker <http://bugs.python.org/issue6070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
