akira added the comment:
count and blocksize are completely different.
*count* specifies how many bytes at most socket.sendfile should sent overall.
It may change the result i.e., it may not be necessary that the file is read
until EOF.
It has the same meaning as *nbytes* parameter
akira added the comment:
I really don't like the use_fallback argument ..
I initially also thought so. But I've suggested the parameter to replace
`(was_os_sendfile_used, os_sendfile_error)` returned value as a *trade off*
between a slight complexity in the interface vs. allowing to detect
Changes by akira 4kir4...@gmail.com:
--
nosy: +akira
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21332
___
___
Python-bugs-list mailing list
akira added the comment:
Should socket.sendfile() always return number of bytes sent because file.tell()
may be changed by something else that uses the same file descriptor?
What happens if the file grows?
Instead of returning `(was_os_sendfile_used, os_sendfile_error)`, you could
specify
Changes by akira 4kir4...@gmail.com:
--
nosy: +akira
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21302
___
___
Python-bugs-list mailing list
New submission from akira:
from email.utils import mktime_tz, parsedate_tz
mktime_tz(parsedate_tz('Thu, 1 Jan 1970 00:00:00 GMT'))
3600.0
It must returns `0` instead of `3600.0` assuming POSIX timestamp.
UTC offsets in 1970 and today are different from each other by one hour in my
local
Changes by akira 4kir4...@gmail.com:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21267
akira added the comment:
I've added the documentation patch with the outdated remark removed from
mktime_tz docs.
--
keywords: +patch
nosy: +akira
type: - behavior
versions: +Python 3.2, Python 3.5
Added file: http://bugs.python.org/file34929/mktime_tz-doc.patch
akira added the comment:
byte must be in range [0, 256)
- it hints at the builtin `range()` -- the intuition works for those who knows
what `range()` does
- it uses the standard math notation for half-open intervals [1] -- no Python
knowledge required (among other things)
- it is not a valid
akira added the comment:
json.dumps works correctly in this case.
Both json/application rfc [1] and ecma json standard [2] say:
All characters may be placed within the quotation marks, except for the
characters that must be escaped: quotation mark (U+0022), reverse solidus
(U+005C
akira added the comment:
You need to escape backslashes inside a Python string literal or use raw-string
literals:
import json
json.loads(r'[[\Residential | Furniture | Cabinets\,\119.99\]]')
[u'[Residential | Furniture | Cabinets,119.99]']
If the backslashes are unintentional
akira added the comment:
From https://docs.python.org/3/glossary.html#term-sequence
An iterable which supports efficient element access using integer indices via
the __getitem__() special method and defines a __len__() method that returns
the length of the sequence.
.parents
akira added the comment:
Also, Richard Oudkerk's claims above about not needing to use fcntl to swap
flags is not correct. It's necessary to not block on reading, even if select
is used. Select just guarantees that there is at least 1 byte or a closed
handle, not that your full read
akira added the comment:
Could `read_nonblocking()`, `write_nonblocking()` raise OSError(EAGAIN) (it
could be named `ResourceTemporarilyUnavailableError`) if read/write would block?
It would allow to distinguish EOF (permanent condition) from read/write would
block (temporarily condition
Changes by akira 4kir4...@gmail.com:
--
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21041
___
___
Python-bugs-list mailing
akira added the comment:
Antoine, I haven't received the e-mail notification.
I've replied to the comments on Rietveld.
Here's the updated patch with the corresponding changes.
--
Added file: http://bugs.python.org/file34594/ssl_cert_time_to_seconds-ps3.patch
New submission from akira:
`pathlib.PurePath.parents` is a sequence [1] but it rejects negative indexes:
from pathlib import PurePath
PurePath('a/b/c').parents[-2]
Traceback (most recent call last):
...
IndexError: -2
Sequences in Python interpret negative indexes as `len(seq) + i
akira added the comment:
I've checked the source code for 3.4; `subprocess` uses `_winapi.CreateProcess`
on Windows [1] that in turn uses `CreateProcessW` [2]. CreateProcessA is not
used.
`Popen` should already support Unicode on Windows though I don't see explicit
tests for non-ascii
akira added the comment:
Related: issue4926 putenv() accepts names containing '=', return value of
unsetenv() not checked
`os.environ.clear()` also fails if the environment contains names with `=`:
import os
os.environ['a=b'] = 'c'
os.environ.clear()
Traceback (most recent call
New submission from akira:
subprocess' stdout pipe is open for *reading* but its value is documented as an
argument for `BaseEventLoop.connect_write_pipe`. It should be
`BaseEventLoop.connect_read_pipe` instead. As it currently is for subprocess'
stderr.
The patch is attached
akira added the comment:
The point of the locale issue is that notBefore, notAfter strings do not
change if your locale changes. You don't need a new regex for each locale.
I've attached ssl_cert_time_seconds.py file that contains example
cert_time_to_seconds(cert_time) implementation
akira added the comment:
Antoine, I've signed the agreement. I've added ssl_cert_time_toseconds.patch
with code, tests, and documention updates.
--
keywords: +patch
Added file: http://bugs.python.org/file34201/ssl_cert_time_to_seconds.patch
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ツ
import utf8
utf8.__doc__
u'\u30c4'
print(utf8.__doc__)
ツ
import
Akira Kitada added the comment:
I suppose this is a duplicate of #1065986.
--
nosy: +akitada
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6625
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 rep...@bugs.python.org
http://bugs.python.org/issue1065986
New submission from akira:
`SubprocessProtocol` is documented to be accessible as
`asyncio.SubprocessProtocol` [1] but it is not included in
`asyncio.protocols.__all__` [2] that leads to `AttributeError`:
python3.4 -c import asyncio; asyncio.SubprocessProtocol
Traceback (most recent
akira added the comment:
gudge, have you seen http://bugs.python.org/msg205860 (the locale issue)?
If you can't fix it; say so, I'll open another issue after this issue is fixed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
akira added the comment:
gudge,
There is also an issue with the current strptime format [1] (`%b %d %H:%M:%S
%Y GMT`). It is locale-dependent and it may fail if a non-English locale is in
effect. I don't know whether I should open a new issue on this or are you going
to fix it too
New submission from akira:
cert_time_to_seconds() uses `time.mktime()` [1] to convert utc time tuple to
seconds since epoch. `mktime()` works with local time. It should use
`calendar.timegm()` analog instead.
Example from the docs [2] is seven hours off (it shows utc offset of the local
Akira Kitada added the comment:
Added meta charset=utf-8 to html pydoc generates.
--
Added file: http://bugs.python.org/file32721/issue1065986-4.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1065986
Akira Kitada added the comment:
Good catch. Fixed.
--
Added file: http://bugs.python.org/file32738/issue1065986-5.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1065986
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 rep...@bugs.python.org
http://bugs.python.org/issue1185124
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 rep...@bugs.python.org
http
Changes by Akira Kitada akit...@gmail.com:
--
nosy: +akitada
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13963
___
___
Python-bugs-list mailing
Changes by Akira Kitada akit...@gmail.com:
--
nosy: +akitada
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1185124
___
___
Python-bugs-list
Akira Kitada added the comment:
Now we have a working fix for 2.7.
Could someone please review the attached patch?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1065986
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
foo
FILE
/tmp/cpython/foo.py
DATA
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__
Changes by Akira Kitada akit...@gmail.com:
--
nosy: +akitada
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12317
___
___
Python-bugs-list mailing
Changes by Akira Kitada akit...@gmail.com:
--
nosy: +akitada
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1065986
___
___
Python-bugs-list
akira added the comment:
The summary assumes that issue 10050 is valid i.e., urlretrieve is
reimplemented using new urlopen and 2.x FancyURLopener is deprecated.
It might not be so [1]. In this case the summary is incorrect.
Old implementation is available as:
opener = FancyURLopener
akira added the comment:
Summary: It is a new behavior. There is no need to change either code or
docs. Though docs could be clarified to be more explicit.
The behavior has been introduced only in 3.3 in revision 53715804dc71
[1] from issue 10050 [2]
It knownly breaks backward
akira added the comment:
Related issue 16409
--
nosy: +akira
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10050
___
___
Python-bugs-list mailing
akira added the comment:
Related issue 16409
--
nosy: +akira
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1490929
___
___
Python-bugs-list
New submission from akira:
import sys
from pickle import dumps, loads
r = xrange(sys.maxsize)
len(r) == sys.maxsize
True
pr = loads(dumps(r))
len(pr) == len(r)
False
pr
xrange(0)
r
xrange(9223372036854775807)
It breaks multiprocessing module:
http
Changes by akira 4kir4...@gmail.com:
--
nosy: +akira
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1602
___
___
Python-bugs-list mailing list
Changes by akira 4kir4...@gmail.com:
--
nosy: +akira
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10278
___
___
Python-bugs-list mailing list
Changes by akira 4kir4...@gmail.com:
--
nosy: +akira
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13643
___
___
Python-bugs-list mailing list
akira 4kir4...@gmail.com added the comment:
Related bug in Java:
http://googleresearch.blogspot.com/2006/06/extra-extra-read-all-about-it-nearly.html
Do not consider any change as trivial:
http://www.solipsys.co.uk/new/BinarySearchReconsidered.html (the author ran
binary search coding
akira 4kir4...@gmail.com added the comment:
TypeError tests can check that an implementation raises a correct exception
type i.e., it doesn't raise ValueError prematurely on invalid format_string
without checking that there is mapping argument.
METH_O does it for CPython. I'm not sure how
New submission from akira 4kir4...@gmail.com:
It seems that some assertions in
Lib/test/test_unicode.py:UnicodeTest.test_format_map do not implement their
intent e.g.,
self.assertRaises(TypeError, '{'.format_map)
self.assertRaises(TypeError, '}'.format_map
Changes by akira 4kir4...@gmail.com:
--
title: fix ''.format_map test - add assertions to implement the intent in
''.format_map test
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13450
Changes by akira 4kir4...@gmail.com:
Removed file:
http://bugs.python.org/file23747/correct-assertions-in-test_format_map.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13450
Changes by akira 4kir4...@gmail.com:
Added file:
http://bugs.python.org/file23748/correct-assertions-in-test_format_map.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13450
New submission from Akira Kitada akit...@gmail.com:
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
New submission from akira 4kir4...@gmail.com:
s/method/module/:
Functionality within this package requires that the ``__main__`` method be
importable by the children.
--
assignee: docs@python
components: Documentation
messages: 134724
nosy: akira, docs@python
priority: normal
akira 4kir4...@gmail.com added the comment:
The test produces a traceback while shrinking a window (increasing the window
size works ok):
Traceback (most recent call last):
File screen-resize-bug-curses.py, line 22, in module
curses.wrapper(main)
File /.../python2.7/curses/wrapper.py
New submission from akira 4kir4...@gmail.com:
Since Python 3.2 logging package doesn't support formatting flags for the
`asctime` keyword, but the documentation uses them. For example in
Doc/library/logging.rst:
FORMAT = '%(asctime)-15s %(clientip)s %(user)-8s %(message)s'
should
New submission from akira 4kir4...@gmail.com:
The line with `LoggerAdapter` is not used in
http://docs.python.org/dev/howto/logging-cookbook.html#using-filters-to-impart-contextual-information
Here's a patch for Doc/howto/logging-cookbook.rst:
doc-logging-cookbook-unused-line-r88640.patch
akira 4kir4...@gmail.com added the comment:
no such file or directory '%s' is misleading if you are trying to open a
readonly file for writing.
The message might be replace by: can't open '%s'
--
___
Python tracker rep...@bugs.python.org
http
akira 4kir4...@gmail.com added the comment:
I've added tests for readonly files. SilentGhost's patch doesn't handle this
case.
--
Added file: http://bugs.python.org/file19806/test_argparse.diff
___
Python tracker rep...@bugs.python.org
http
akira 4kir4...@gmail.com added the comment:
Attached patch for argparse.py (argparse.diff -- without tests, see tests in
test_argparse.diff) where ValueError is raises in FileType.__call__ and
additional details printed on ArgumentError
--
Added file: http://bugs.python.org/file19807
akira 4kir4...@gmail.com added the comment:
updated patch on http://codereview.appspot.com/3251041/
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9509
akira 4kir4...@gmail.com added the comment:
Simplified the patch and added test for a non-existent file in issue9509.patch
The test `py3k/python -m test.regrtest test_argparse` fails without the patch
and succeeds with it.
The docs in Doc/library/argparse.rst and Lib/argparse.py don't need
Changes by Akira Kitada akit...@gmail.com:
Removed file: http://bugs.python.org/file13673/issue5736.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5736
Changes by Akira Kitada akit...@gmail.com:
Removed file: http://bugs.python.org/file13674/issue5736.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5736
Changes by Akira Kitada akit...@gmail.com:
Removed file: http://bugs.python.org/file13682/test_issue5736.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5736
Changes by Akira Kitada akit...@gmail.com:
Removed file: http://bugs.python.org/file13676/issue5736.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5736
Akira Kitada akit...@gmail.com 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
Akira Kitada akit...@gmail.com 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/issue10052.diff
Akira Kitada akit...@gmail.com 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 not provide them
New submission from Akira Kitada akit...@gmail.com:
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/akitada/src
Akira Kitada akit...@gmail.com added the comment:
It works fine with USE_SEMAPHORES commented out.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10062
Akira Kitada akit...@gmail.com added the comment:
The patch does fix the build error.
Thank you!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10062
Akira Kitada akit...@gmail.com 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
New submission from Akira Kitada akit...@gmail.com:
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
Python
New submission from Akira Kitada akit...@gmail.com:
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 -Wall
-Wstrict
Akira Kitada akit...@gmail.com added the comment:
This patch fixes this.
--
keywords: +patch
Added file: http://bugs.python.org/file19173/issue10054.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10054
New submission from Akira Kitada akit...@gmail.com:
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
Akira Kitada akit...@gmail.com 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
Akira Kitada akit...@gmail.com 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
New submission from akira 4kir4...@gmail.com:
$ python3.1 -c'import math; f = math.log(4,2); print(int(f),
f.as_integer_ratio())'
2 (2, 1)
$ python3.2 -c'import math; f = math.log(4,2); print(int(f),
f.as_integer_ratio())'
1 (9007199254740991, 4503599627370496)
Python 3.2a2+ (py3k:85028, Sep
akira 4kir4...@gmail.com added the comment:
No, it's not really a bug: math.log(x, 2) isn't an atomic operation:
It is not a bug, but values of math.log(4) differs between 3.1 and 3.2
i.e., math.log(4.0) in 3.2 returns value that is consistent with
math.log(4) in 3.1 but math.log(4) in 3.2
Changes by akira 4kir4...@gmail.com:
Added file: http://bugs.python.org/file19031/test_log_power_two.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9959
Changes by akira 4kir4...@gmail.com:
--
type: behavior - feature request
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9959
___
___
Python-bugs
akira 4kir4...@gmail.com added the comment:
Minor notes:
msg107186:
1. The constructor now accepts only whole number of minutes in [-23:59,
23:59] range.
rfc 3339 provides the following example:
1937-01-01T12:00:27.87+00:20
This represents the same instant of time as noon, January
New submission from akira 4kir4...@gmail.com:
Currently it is not obvious that os.devnull works on Windows.
--
assignee: d...@python
components: Documentation
files: doc-os-devnull-windows-r81160.diff
keywords: patch
messages: 105688
nosy: akira, d...@python
priority: normal
severity
New submission from akira 4kir4...@gmail.com:
`messges` should be replaced by `messages` on
http://docs.python.org/dev/library/argparse.html#upgrading-optparse-code page.
--
assignee: d...@python
components: Documentation
messages: 104144
nosy: akira, d...@python
severity: normal
Akira Kitada akit...@gmail.com 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.html#index-CXX-848
--
nosy
Akira Kitada akit...@gmail.com added the comment:
I think this is duplicate of issue858809.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1294959
Akira Kitada akit...@gmail.com added the comment:
I think this is duplicate of issue858809.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1019715
Tanaka Akira a...@fsij.org added the comment:
src/if_python.c in vim-7.2 has a comment:
/* Set sys.argv[] to avoid a crash in warn(). */
I think the crash is follows.
% python
Python 2.5.2 (r252:60911, Jan 4 2009, 17:40:26)
[GCC 4.3.2] on linux2
Type help, copyright, credits or license
Akira Kitada akit...@gmail.com 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
Changes by Akira Kitada akit...@gmail.com:
--
nosy: +akitada
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6331
___
___
Python-bugs-list mailing
Akira Kitada akit...@gmail.com 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
Akira Kitada akit...@gmail.com 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
Akira Kitada akit...@gmail.com 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'] = 'v2';
for i in dumb: print i; break
...
k2
for i in dumb: print
New submission from Akira Kitada akit...@gmail.com:
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
...
for k in d: print k, d[k]
...
Traceback (most recent call last
Akira Kitada akit...@gmail.com 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
Akira Kitada akit...@gmail.com 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 rep
201 - 300 of 436 matches
Mail list logo
