Akira Kitada added the comment:
Good point. I looked at some Python files but, as you pointed out,
I couldn't find ones what follow the recommendation.
In some files there is a blank line after a docstring but it seemed
it's not because it "is written as a number of sections"
Akira Kitada added the comment:
Guido is with me :)
On Wed, Oct 22, 2014 at 2:16 AM, Guido van Rossum wrote:
> I think the argument is about the blank line between the "class" line and
> the docstring. I agree with Akira that very few packages follow this style,
> and I thi
New submission from Akira Kitada:
The PEP 257 says:
Insert a blank line before and after all docstrings (one-line or multi-line)
that document a class
Looking at stdlib and popular open source software, I couldn't find packages
that follow this style, so I think this is not rea
Akira Kitada added the comment:
I tried pydoc_2.7.patch with the following test file and
found source_synopsis returns \x escaped string instead of \u escaped one.
# -*- coding: utf-8 -*-
u"""ツ"""
class Spam(object):
u"""ツ"""
Akira Kitada added the comment:
I suppose this is a duplicate of #1065986.
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue6625>
___
___
Pytho
Akira Kitada added the comment:
Made a few more adjustments to fix things r.david.murray pointed out.
--
Added file: http://bugs.python.org/file33316/issue1065986-6.patch
___
Python tracker
<http://bugs.python.org/issue1065
Akira Kitada added the comment:
Good catch. Fixed.
--
Added file: http://bugs.python.org/file32738/issue1065986-5.patch
___
Python tracker
<http://bugs.python.org/issue1065
Akira Kitada added the comment:
Added to html pydoc generates.
--
Added file: http://bugs.python.org/file32721/issue1065986-4.patch
___
Python tracker
<http://bugs.python.org/issue1065
Akira Kitada added the comment:
Do you have any plan to work on patch for 2.7?
Apparently your patch is only for 3.x.
--
___
Python tracker
<http://bugs.python.org/issue1185
Akira Kitada added the comment:
Now we have a working fix for 2.7.
Could someone please review the attached patch?
--
___
Python tracker
<http://bugs.python.org/issue1065
Changes by Akira Kitada :
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue1185124>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Akira Kitada :
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue13963>
___
___
Python-bugs-list mailing list
Unsubscribe:
Akira Kitada added the comment:
Updated the previous patch to test unicode strings in
__{version,date,author,credits}__ don't crash.
--
Added file: http://bugs.python.org/file31832/issue1065986-3.patch
___
Python tracker
<http://bugs.py
Akira Kitada added the comment:
With this patch applied, the example from issue15791 works fine.
$ echo "__author__ = u'Michele Orr\xf9'" > foo.py && ./python -c "import foo;
print foo.__author__; help(foo)"
Michele Orrù
Help on module foo:
NAME
Akira Kitada added the comment:
Attaching a modified version of issue1065986.patch.
The differences are:
- Added _binstr(), which is str() that works with unicode objects.
- Changed getdoc() to return encoded docstrings/comments
- Used _binstr() to convert __version__, __date__, __author__ and
Changes by Akira Kitada :
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue12317>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Akira Kitada :
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue1065986>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Akira Kitada :
Modules/mmapmodule.c contains code that makes it incompatible with C89 compiler.
People using recent gcc can check this by running following commands.
$ ./configure CFLAGS='-Wdeclaration-after-statement' && make
Attached patch fixes th
Akira Kitada added the comment:
This patch is specifically targeted at FreeBSD 4.
tested on FreeBSD 4.11 and OS X 10.6.4
I don't know how to accommodate SGI IRIX's case.
--
keywords: +patch
Added file: http://bugs.python.org/file19254/issue
Akira Kitada added the comment:
This patch just uses PyObject_GetIter to get an iter.
(I just copied the idea from issue9523)
--
nosy: +ysj.ray
versions: +Python 3.2 -Python 2.7
Added file: http://bugs.python.org/file19250/issue5736.diff
___
Python
Changes by Akira Kitada :
Removed file: http://bugs.python.org/file13676/issue5736.diff
___
Python tracker
<http://bugs.python.org/issue5736>
___
___
Python-bugs-list m
Changes by Akira Kitada :
Removed file: http://bugs.python.org/file13682/test_issue5736.diff
___
Python tracker
<http://bugs.python.org/issue5736>
___
___
Python-bug
Changes by Akira Kitada :
Removed file: http://bugs.python.org/file13674/issue5736.diff
___
Python tracker
<http://bugs.python.org/issue5736>
___
___
Python-bugs-list m
Changes by Akira Kitada :
Removed file: http://bugs.python.org/file13673/issue5736.diff
___
Python tracker
<http://bugs.python.org/issue5736>
___
___
Python-bugs-list m
Akira Kitada added the comment:
I understand FreeBSD 4.x is old platform (4.11, the last 4.x series, is
released 5 years ago) but, in my opinion, as long as it does not make Python
code cluttered, supporting old platforms is not that bad idea.
Anyway, I would like to leave the decision to
Akira Kitada added the comment:
The patch does fix the build error.
Thank you!
--
___
Python tracker
<http://bugs.python.org/issue10062>
___
___
Python-bug
Akira Kitada added the comment:
It works fine with USE_SEMAPHORES commented out.
--
___
Python tracker
<http://bugs.python.org/issue10062>
___
___
Python-bug
New submission from Akira Kitada :
Build fails on FreeBSD 4 due to the lack of sem_timedwait.
"""
gcc -pthread -Wl,--export-dynamic -o python Modules/python.o libpython3.2.a
-lutil -lm
libpython3.2.a(thread.o): In function `PyThread_acquire_lock_timed':
/home/aki
Akira Kitada added the comment:
Forgot to mention that there's no _MAX macro for exact-width integer types.
$ egrep -r 'INT[0-9].*_MAX' /usr/include/ | wc -l
0
How about adding those macros when the system does n
Akira Kitada added the comment:
It seems this problem was introduced by a patch in issue7211.
3.1 branch does not have this problem because that patch was not applied to
release31-maint. Is this intentional?
--
versions: +Python 3.2
___
Python
Akira Kitada added the comment:
> 1. Have you tested this with Python 3.x at all? I'd expect the same issues
> to show up for Python 3.1 and 3.2.
Yes, I can reproduce this in 2.7, 3.1 and 3.2.
> 2. Also, do you have the relevant configure output to hand? On my machine,
>
New submission from Akira Kitada :
I found some C99 code in _json.c.
Attached patch makes it C89.
The C99 part is only used for ucs4 Python. That's probably the reason
it's overlooked.
--
components: Build
files: _json.c.diff
keywords: patch
messages: 118255
nosy: akitad
Akira Kitada added the comment:
This patch fixes this.
--
keywords: +patch
Added file: http://bugs.python.org/file19173/issue10054.diff
___
Python tracker
<http://bugs.python.org/issue10
New submission from Akira Kitada :
Some platforms have uintptr_t in inttypes.h but Python bulid system
assumes it's defined in stdint.h and it causes build failure:
"""
building 'select' extension
gcc -pthread -fPIC -fno-strict-aliasing -g -O2 -DNDEBUG -g -O3
New submission from Akira Kitada :
Building Python 2.7 fails on FreeBSD 4.11 with gcc 2.95.4 as below:
"""
gcc -pthread -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -o
Python/dtoa.o Python/dtoa.c
Py
Akira Kitada added the comment:
I think this is duplicate of issue858809.
--
___
Python tracker
<http://bugs.python.org/issue1019715>
___
___
Python-bugs-list m
Akira Kitada added the comment:
I think this is duplicate of issue858809.
--
___
Python tracker
<http://bugs.python.org/issue1294959>
___
___
Python-bugs-list m
Akira Kitada added the comment:
Aren't CC and CXX variables just for compilers?
"""
CC
Program for compiling C programs; default `cc'.
CXX
Program for compiling C++ programs; default `g++'.
"""
http://www.gnu.org/software/make/manual/make.
Changes by Akira Kitada :
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue6331>
___
___
Python-bugs-list mailing list
Unsubscribe:
Akira Kitada added the comment:
Thanks for this great work!
Does Regexp 2.7 include Unicode Scripts support?
http://www.regular-expressions.info/unicode.html
Perl and Ruby support it and it's pretty handy.
--
nosy: +akitada
___
Python tr
Akira Kitada added the comment:
Yes, using a static variable there is wrong and
actually I'm now working on "dbm_iterobject" just as Martin suggested.
dbm iterator should behave just like one in dict.
I think I can use Objects/dictobject.c as a good example for this.
Attached i
Akira Kitada added the comment:
Of course iter should work in the same way in all dbm modules.
iter in dbm/gdbm should work like dumbdbm's iter.
>>> dumb = dumbdbm.open('foo', 'n')
>>> dumb['k1'] = 'v1';dumb['k2'] = '
Akira Kitada added the comment:
Here's another patch which addsd iter to dbm and gdbm.
Note that dbm and gdbm C API is a little different.
gdbm_nextkey requires key for its argument, dbm_nextkey don't.
So I had to use for gdbm an static variable that points to the current
pos
Akira Kitada added the comment:
Revised patch adds firstkey and nextkey to dbm.
Now the internal pointer can be reset with firstkey.
--
Added file: http://bugs.python.org/file13674/issue5736.diff
___
Python tracker
<http://bugs.python.org/issue5
Akira Kitada added the comment:
Attached is a patch that adds the iterator protocol.
Now it can be interated through like:
>>> for k in d: print k, d[k]
...
key1 vale1
key3 vale3
key0 vale0
key2 vale2
key4 vale4
The problem is there is no way to get the internal pointer back to the
New submission from Akira Kitada :
In Python 2.6, dbm modules othar than bsddb don't support the iterator
protocol.
>>> import dbm
>>> d = dbm.open('spam.dbm', 'c')
>>> for k in range(5): d["key%d" % k] = "value%d" % k
Akira Kitada added the comment:
I updated the patch.
Mine only changes log.py.
--
nosy: +akitada
Added file: http://bugs.python.org/file13260/remove-custom-log-revised.diff
___
Python tracker
<http://bugs.python.org/issue3
Akira Kitada added the comment:
The patch looks ok to me.
Python 2.3 - 2.6 seem working fine with this patch, too.
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue3
Changes by Akira Kitada :
--
title: bdist_rpm assumes python -> bdist_rpm should enable --fix-python by
default
___
Python tracker
<http://bugs.python.org/iss
Changes by Akira Kitada :
--
components: +Windows
___
Python tracker
<http://bugs.python.org/issue5235>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Akira Kitada :
--
assignee: -> tarek
components: +Windows
nosy: +tarek
type: -> crash
___
Python tracker
<http://bugs.python.org/issue4918>
___
__
Changes by Akira Kitada :
--
assignee: -> tarek
components: +Windows
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue4480>
___
___
Python-bugs-lis
Changes by Akira Kitada :
--
type: -> feature request
versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 -Python 2.4
___
Python tracker
<http://bugs.python.org/issue1
Akira Kitada added the comment:
'ignore' was introduced in Python 2.6 but distutils has to keep Python
2.3 compatible.
See: http://bugs.python.org/issue5052
So I guess you have to wait some more years before
dropping distutils.dir_util and distutils.file_util.
--
nosy
Changes by Akira Kitada :
--
assignee: -> tarek
components: +Windows
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue4214>
___
___
Python-bugs-lis
Akira Kitada added the comment:
There are two options for that in bdist_rpm.
--python path to Python interpreter to hard-code in the .spec
file (default: "python")
--fix-python hard-code the exact path to the curr
Akira Kitada added the comment:
Updated issue4010 to honor os.environ['CPPFLAGS'].
Added file: http://bugs.python.org/file13212/issue4010.diff
___
Python tracker
<http://bugs.python.
Changes by Akira Kitada :
Removed file: http://bugs.python.org/file12954/issue4010.diff
___
Python tracker
<http://bugs.python.org/issue4010>
___
___
Python-bugs-list m
Changes by Akira Kitada :
--
assignee: -> tarek
components: +Windows
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue2200>
___
___
Python-bugs-lis
Changes by Akira Kitada :
--
assignee: -> tarek
components: +Windows
nosy: +tarek
type: -> compile error
___
Python tracker
<http://bugs.python.org/
Changes by Akira Kitada :
--
assignee: -> tarek
components: +Windows
nosy: +tarek
type: -> compile error
___
Python tracker
<http://bugs.python.org/
Akira Kitada added the comment:
3rd party C modules are put in site-packages,
so just having importer of 64-bit python look at lib64-dynload is not
enough for solving this.
To work around this problem, I did some hacks on my local Python to look
at lib and lib64. It worked, but just as
New submission from Akira Kitada :
As written in its README, "Distutils must remain compatible with 2.3",
but it isn't. Attached patch fixes this.
--
assignee: tarek
components: Distutils
files: python23_compat.diff
keywords: patch
messages: 82920
nosy: akitada, tarek
s
Akira Kitada added the comment:
If I'm not mistaken, this bug seems to be fre-introduced in
"release30-maint/Modules/python.c".
It could be fixed in just as it was before.
--
components: +Interpreter Core -None
nosy: +akitada
type: -> behavior
versions: +Python 2.6,
Changes by Akira Kitada :
--
nosy: +tarek
type: -> behavior
versions: +Python 2.7, Python 3.1 -Python 2.3, Python 2.4, Python 2.5
___
Python tracker
<http://bugs.python.org/issue
Changes by Akira Kitada :
--
assignee: -> tarek
components: +Build
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue1887>
___
___
Python-bugs-lis
Changes by Akira Kitada :
--
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue1254718>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Akira Kitada :
--
type: -> feature request
versions: +Python 2.7, Python 3.1 -Python 2.5, Python 2.6
___
Python tracker
<http://bugs.python.org/issue1
Changes by Akira Kitada :
--
versions: +Python 2.7, Python 3.1 -Python 2.6
___
Python tracker
<http://bugs.python.org/issue1692592>
___
___
Python-bugs-list mailin
Changes by Akira Kitada :
--
assignee: -> tarek
nosy: +tarek
versions: +Python 2.7, Python 3.1 -Python 2.6
___
Python tracker
<http://bugs.python.org/issue
Changes by Akira Kitada :
--
components: +Windows
___
Python tracker
<http://bugs.python.org/issue1285>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Akira Kitada :
--
nosy: +tarek
type: -> behavior
versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 -Python 2.5
___
Python tracker
<http://bugs.python.org/issue1
Changes by Akira Kitada :
--
nosy: +tarek
type: -> behavior
versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 -Python 2.4
___
Python tracker
<http://bugs.python.org/issue
Changes by Akira Kitada :
--
assignee: -> tarek
components: +Windows
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue1635363>
___
___
Python-
Changes by Akira Kitada :
--
nosy: +tarek
type: -> feature request
versions: +Python 2.7, Python 3.1 -Python 2.4
___
Python tracker
<http://bugs.python.org/issue1
Changes by Akira Kitada :
--
nosy: +tarek
type: -> feature request
versions: +Python 2.7, Python 3.1 -Python 2.3
___
Python tracker
<http://bugs.python.org/issue1
Changes by Akira Kitada :
--
nosy: +tarek
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue1274324>
___
___
Python-bugs-list mailing list
Un
Changes by Akira Kitada :
--
nosy: +tarek
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue1289136>
___
___
Python-bugs-list mailing list
Un
Akira Kitada added the comment:
Is this problem already closed?
--
nosy: +akitada, tarek
___
Python tracker
<http://bugs.python.org/issue957381>
___
___
Pytho
Changes by Akira Kitada :
--
nosy: +tarek
type: -> behavior
versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 -Python 2.4
___
Python tracker
<http://bugs.python.org/issue1
Akira Kitada added the comment:
Duplicate of issue1169193
--
nosy: +akitada, tarek
___
Python tracker
<http://bugs.python.org/issue644744>
___
___
Python-bug
Akira Kitada added the comment:
Duplicate of issue644744
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue1169193>
___
___
Python-bugs-list m
Changes by Akira Kitada :
--
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue809846>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Akira Kitada :
--
nosy: +tarek
type: -> behavior
versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 -Python 2.3
___
Python tracker
<http://bugs.python.org/issue1
Akira Kitada added the comment:
duplicate of issue755286
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue1035576>
___
___
Python-bugs-list m
Akira Kitada added the comment:
Duplicate of issue1035576
--
nosy: +akitada, tarek
___
Python tracker
<http://bugs.python.org/issue755286>
___
___
Python-bug
Changes by Akira Kitada :
--
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue818201>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Akira Kitada :
--
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue1035576>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Akira Kitada :
--
nosy: +tarek
type: -> feature request
versions: +Python 2.7, Python 3.1 -Python 2.3
___
Python tracker
<http://bugs.python.org/issue1
Changes by Akira Kitada :
--
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue1222585>
___
___
Python-bugs-list mailing list
Unsubscribe:
Akira Kitada added the comment:
I don't think that's not depends keyword is used for.
I assume explanation on issue5158 is the way that "depends" is supposed
to be used.
--
nosy: +akitada, tarek
___
Python tracker
<
Changes by Akira Kitada :
--
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue1718574>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Akira Kitada :
--
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue1004696>
___
___
Python-bugs-list mailing list
Unsubscribe:
Akira Kitada added the comment:
Same with issue2624?
--
nosy: +akitada, tarek
___
Python tracker
<http://bugs.python.org/issue1016626>
___
___
Python-bugs-list m
Akira Kitada added the comment:
seems this is already fixed in issue1046644.
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue828336>
___
___
Akira Kitada added the comment:
Same with issue1016626?
--
nosy: +akitada
___
Python tracker
<http://bugs.python.org/issue2624>
___
___
Python-bugs-list mailin
Changes by Akira Kitada :
--
nosy: +tarek
type: -> feature request
___
Python tracker
<http://bugs.python.org/issue1326113>
___
___
Python-bugs-list mai
Akira Kitada added the comment:
I don't understand the use case of that option.
--
nosy: +akitada, tarek
___
Python tracker
<http://bugs.python.org/issu
Akira Kitada added the comment:
I think it still need to be clarified in PEP that Keywords field accept
comma-or-space-separated values.
___
Python tracker
<http://bugs.python.org/issue1294
Akira Kitada added the comment:
s/PEP341/PEP345/?
--
nosy: +akitada, tarek
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue1294032>
___
_
1 - 100 of 188 matches
Mail list logo
