[issue4149] Py_BuildValue and "y" format unit
New submission from Kandalintsev Alexandre <[EMAIL PROTECTED]>: Hello! 'y' format unit in Py_BuildValue undocumented. However it's described in PyArg_ParseTuple. -- assignee: georg.brandl components: Documentation messages: 74989 nosy: exe, georg.brandl severity: normal status: open title: Py_BuildValue and "y" format unit versions: Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4149> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4504] Doc/includes out of date
New submission from Kandalintsev Alexandre <[EMAIL PROTECTED]>:
Hello!
Doc/includes/noddy.c and all other uses Py_InitModule3 which is removed
from py3k.
noddy2.c doesn't compile("noddy2.c:16: error: ‘Noddy’ has no member
named ‘ob_type’").
--
assignee: georg.brandl
components: Documentation
messages: 76828
nosy: exe, georg.brandl
severity: normal
status: open
title: Doc/includes out of date
type: compile error
versions: Python 3.0
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4504>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4505] ob_size not removed from docs
New submission from Kandalintsev Alexandre <[EMAIL PROTECTED]>: Hello! In http://docs.python.org/dev/3.0/extending/newtypes.html we see ob_size in object definition. But if we are look on PyTypeObject in ./Include/object.h we will find that there no ob_size defined. So we must remove this string from noddy_NoddyType definition or segfault will occur: 0, /*ob_size*/ -- assignee: georg.brandl components: Documentation messages: 76829 nosy: exe, georg.brandl severity: normal status: open title: ob_size not removed from docs versions: Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4505> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4535] Build / Test Py3K failed on Ubuntu 8.10
Kandalintsev Alexandre <[EMAIL PROTECTED]> added the comment: My results on ubuntu 8.10 x86(with debug features enabled) on Python 3.1a0 (py3k:67586, Dec 5 2008, 19:39:50): 298 tests OK. 23 tests skipped: test_codecmaps_cn test_codecmaps_hk test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_curses test_dbm_gnu test_dbm_ndbm test_kqueue test_nis test_normalization test_ossaudiodev test_pep277 test_socketserver test_startfile test_tcl test_timeout test_urllib2net test_urllibnet test_winreg test_winsound test_xmlrpc_net test_zipfile64 3 skips unexpected on linux2: test_tcl test_dbm_ndbm test_dbm_gnu [870063 refs] May be problems fixed in current trunk(http://svn.python.org/projects/ python/branches/py3k)? -- nosy: +exe ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4535> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4576] "Defining new types" little outdated
New submission from Kandalintsev Alexandre <[EMAIL PROTECTED]>: Hello! It's need to little update "Defining new types" documentation section in py3.0 and py3.1: - self->ob_type->tp_free((PyObject*)self); + Py_TYPE(self)->tp_free((PyObject *)self); -- assignee: georg.brandl components: Documentation messages: 77225 nosy: exe, georg.brandl severity: normal status: open title: "Defining new types" little outdated versions: Python 3.0, Python 3.1 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4576> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4535] Build / Test Py3K failed on Ubuntu 8.10
Kandalintsev Alexandre <[EMAIL PROTECTED]> added the comment: Rob, could you repeat this test on trunk version of python? ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4535> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4737] documentation and noddy*.c
New submission from Kandalintsev Alexandre : Hello! 1) In http://docs.python.org/3.0/extending/extending.html we see: = Note that PyMODINIT_FUNC declares the function as void return type = But thats not true, it's defined as PyObject*. I think this is outdated info in documentation. 2) In Doc/includes/noddy*.c assumed that PyMODINIT_FUNC returns nothing but this wrong. If you try "python3.1 -c 'import noddy'" you will see segfault. This patch will fix this problem: --- ./noddy.c 2008-12-24 17:09:36.424870738 +0300 +++ ./noddy.c 2008-12-24 17:18:01.524869143 +0300 @@ -52,4 +52,6 @@ Py_INCREF(&noddy_NoddyType); PyModule_AddObject(m, "Noddy", (PyObject *)&noddy_NoddyType); + +return m; } Other noddy*.c files are also requiring this patch. -- assignee: georg.brandl components: Demos and Tools, Documentation messages: 78260 nosy: exe, georg.brandl severity: normal status: open title: documentation and noddy*.c versions: Python 3.0, Python 3.1 ___ Python tracker <http://bugs.python.org/issue4737> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4800] little inaccuracy in Py_ssize_t explanation
New submission from Kandalintsev Alexandre : Documentation says that There’s no chance that the reference count can overflow; at least as many bits are used to hold the reference count as there are distinct memory locations in virtual memory (assuming sizeof(Py_ssize_t) >= sizeof(void*)). Thus, the reference count increment is a simple operation. But Py_ssize_t is a signed type so in case of sizeof(Py_ssize_t) == sizeof (void*)) it can only reference a half of memmory :). But because any python object consumes much more than 2bytes this is not a problem. -- assignee: georg.brandl components: Documentation messages: 78695 nosy: exe, georg.brandl severity: normal status: open title: little inaccuracy in Py_ssize_t explanation versions: Python 3.0, Python 3.1 ___ Python tracker <http://bugs.python.org/issue4800> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5096] strange thing after call PyObject_CallMethod
New submission from Kandalintsev Alexandre : When unhandled in python code exception occurs in PyObject_CallMethod frame_dealloc() (Objects/frameobject.c:422) not called. Even if I call PyErr_Print(). But if I call PyErr_Clear() then all okay. Documentation says that both this functions doing same work(http://docs.python.org/3.0/c-api/ exceptions.html). As we see thats not true or not all nuances documented. Examples and more on this mailing list: http://groups.google.com/group/comp.lang.python/browse_thread/ thread/19316b3effa37d2d -- components: Interpreter Core messages: 80757 nosy: exe severity: normal status: open title: strange thing after call PyObject_CallMethod type: behavior versions: Python 3.0, Python 3.1 ___ Python tracker <http://bugs.python.org/issue5096> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5096] strange thing after call PyObject_CallMethod
Kandalintsev Alexandre added the comment: Thank you for your activity. This feature drank alot of my blood. Please document this or change behavior. PS Older python versions may be also affected so changing behavior may brake existing code :( ___ Python tracker <http://bugs.python.org/issue5096> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5097] asyncore.dispatcher_with_send undocumented
New submission from Kandalintsev Alexandre : Hello! asyncore.dispatcher_with_send undocumented in all python versions -- assignee: georg.brandl components: Documentation messages: 80763 nosy: exe, georg.brandl severity: normal status: open title: asyncore.dispatcher_with_send undocumented ___ Python tracker <http://bugs.python.org/issue5097> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5097] asyncore.dispatcher_with_send undocumented
Kandalintsev Alexandre added the comment: Ok, I'll try :). I'll send it today or tomorrow. ___ Python tracker <http://bugs.python.org/issue5097> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5097] asyncore.dispatcher_with_send undocumented
Kandalintsev Alexandre added the comment: This is my explanation of dispatcher_with_send. As my english is far from perfect and I'm not expirienced writing documentation you need to review it and fix my mistakes. class asyncore.dispatcher_with_send This is class based on asyncore.dispatcher. The only difference that unlike dispatcher.send which is direct mean to the socket.send() send() of this class uses buffered io. At first all outgoing data saved to the buffer and later it will send when socket becomes avaliable for write. Thus dispatcher_with_send.send() will never return EWOULDBLOCK error. Also you shuldn't overrdie writable() method as in this dispatcher it will automatically return convient value depending weither output buffer empty or not. -- versions: +Python 2.4, Python 2.5, Python 2.6, Python 2.7, Python 3.0, Python 3.1 ___ Python tracker <http://bugs.python.org/issue5097> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6969] configparser
New submission from Kandalintsev Alexandre :
Hello! Seems configparser is broken in recent versions of py3k. Please also
check older
versions of python.
$ python3 ./cfgexample.py
Traceback (most recent call last):
File "./cfgexample.py", line 9, in
config.write(configfile)
File "/usr/local/py3k/lib/python3.2/configparser.py", line 394, in write
fp.write("[%s]\n" % section)
TypeError: must be bytes or buffer, not str
$ cat ./cfgexample.py
import configparser
config = configparser.RawConfigParser()
config.add_section('Section1')
config.set('Section1', 'int', '15')
with open('example.cfg', 'wb') as configfile:
config.write(configfile)
$ python3 --version
Python 3.2a0
I've built this version of python:
$ hg head
changeset: 4765:488e143fad23
branch: py3k
tag: tip
user:tarek.ziade
date:Tue Sep 22 12:08:13 2009 +0200
summary: [svn r75013] Merged revisions 74812 via svnmerge from
--
components: Library (Lib)
messages: 92993
nosy: exe
severity: normal
status: open
title: configparser
versions: Python 3.2
___
Python tracker
<http://bugs.python.org/issue6969>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5097] asyncore.dispatcher_with_send undocumented
Kandalintsev Alexandre added the comment: Please don't keep this bug open :( -- ___ Python tracker <http://bugs.python.org/issue5097> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5966] unnecessary hardlink
New submission from Kandalintsev Alexandre : Hello! After installing py3k:72466 I found that python3 is hardlink to python3.1: $ ls -lai python* 34614 -rwxr-xr-x 2 root root 3625145 2009-05-08 11:10 python3 34614 -rwxr-xr-x 2 root root 3625145 2009-05-08 11:10 python3.1 38299 -rwxr-xr-x 1 root root1406 2009-05-08 11:10 python3.1-config 34616 lrwxrwxrwx 1 root root 16 2009-05-08 11:10 python3-config -> python3.1-config I'm expecting symlink python3 pointing to python3.1(as python is symlink to python2.5 in my system). It's much easy to manage symlinks than hardlinks. -- components: Installation messages: 87428 nosy: exe severity: normal status: open title: unnecessary hardlink type: behavior versions: Python 3.1 ___ Python tracker <http://bugs.python.org/issue5966> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6052] for-loop doesn't work with -c
New submission from Kandalintsev Alexandre : Hello! I found this problem: $ python3 -c 'import sys; for line in sys.stdout: pass' File "", line 1 import sys; for line in sys.stdout: pass ^ SyntaxError: invalid syntax Without import-statement this work great. Also code 'import sys; pass' works too. -- components: Interpreter Core messages: 88024 nosy: exe severity: normal status: open title: for-loop doesn't work with -c versions: Python 2.5, Python 2.6, Python 2.7, Python 3.0, Python 3.1, Python 3.2 ___ Python tracker <http://bugs.python.org/issue6052> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
