New submission from Vladimir Rutsky:
"Specifying custom filter chains" section contains:
> It only supports a single The delta filter supports only one option, dist.
Probably should be just:
> The delta filter supports only one option, dist.
--
assignee: docs@p
Changes by Vladimir Rutsky <altsy...@gmail.com>:
--
nosy: +rutsky
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue13610>
___
__
New submission from Vladimir Rutsky:
Looks like there is no need to place space separators after numbers:
$ python3.5 -c "print(1and 0)"
0
$ python3.5 -c "print([1for i in range(1)])"
[1]
Not sure is this a bug or a feature, but I would expect that this should be
Synta
New submission from Vladimir Rutsky:
In Python 3.4.3 with enabled asyncio debug a function is
wrapped using the following code in @asyncio.coroutine:
@functools.wraps(func)
def wrapper(*args, **kwds):
w = CoroWrapper(coro(*args, **kwds), func)
if w._source_traceback:
del w
New submission from Vladimir Rutsky:
Return of @asyncio.coroutine-wrapped coroutine object from
@asyncio.coroutine-wrapped coroutine fails if asyncio debug is enabled.
Consider following example:
@asyncio.coroutine
def outer_coro():
@asyncio.coroutine
def inner_coro():
return
Changes by Vladimir Rutsky <rutsky.vladi...@gmail.com>:
--
title: Return of asyncio.coroutine from asyncio.coroutine don't work in with
enabled debug -> Return of asyncio.coroutine from asyncio.coroutine doesn't
work in with enab
Changes by Vladimir Rutsky <rutsky.vladi...@gmail.com>:
--
title: Return of asyncio.coroutine from asyncio.coroutine doesn't work in with
enabled debug -> Return of asyncio.coroutine from asyncio.coroutine doesn't
work with enabled asyn
New submission from Vladimir Rutsky:
In 3.4 docs after generator.close() description there is strange dot:
http://docs.python.org/3.4/reference/expressions.html#generator.close
Looks like it's due to following code in Doc/reference/expressions.rst:452:
.. class:: .
This line should be removed
New submission from Vladimir Rutsky:
http://docs.python.org/2/library/repr.html page contains several links on
built-in function `repr()` (search for built-in repr() on page), but links
goes to `Repr.repr()` functions of `Repr` module instead of
http://docs.python.org/library/functions.html
Changes by Vladimir Rutsky altsy...@gmail.com:
--
nosy: +rutsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18243
___
___
Python-bugs-list
New submission from Vladimir Rutsky:
References to built-in function repr() links to repr module
(http://docs.python.org/2/library/repr.html#module-repr), but must link to
description in http://docs.python.org/2/library/functions.html.
It can be at least in http://docs.python.org/2/library
Changes by Vladimir Rutsky altsy...@gmail.com:
--
nosy: +rutsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1744382
___
___
Python-bugs-list
Changes by Vladimir Rutsky rutsky.vladi...@gmail.com:
--
nosy: +vrutsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8800
___
___
Python-bugs
Vladimir Rutsky added the comment:
Yes, I managed to pass and operate with matrices of complex numbers to pure C
and Fortran programs by using Numpy and their ctype adapters (only for whole
matrices, they don't provide c_complex type; in general see
http://www.scipy.org/Cookbook/Ctypes
New submission from Vladimir Rutsky:
It would be nice if Python will be able to access variables with C99 complex
types through ctypes module.
--
components: ctypes
messages: 179378
nosy: rutsky
priority: normal
severity: normal
status: open
title: Add support for C99 complex type
New submission from Vladimir Rutsky:
Please see attached patch for details.
--
files: quote_typo.patch
keywords: patch
messages: 173594
nosy: vrutsky
priority: normal
severity: normal
status: open
title: typo in error message in pstats.py
versions: Python 2.7
Added file: http
New submission from Vladimir Rutsky:
re module documentation says:
Match Objects always have a boolean value of :const:`True`, so that you can
test
whether e.g. :func:`match` resulted in a match with a simple if statement.
which is confusing - matched objects have boolean value True
Changes by Vladimir Rutsky altsy...@gmail.com:
--
nosy: +rutsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13857
___
___
Python-bugs-list
New submission from Vladimir Rutsky altsy...@gmail.com:
There is a typo in urllib module documentation: missing space after dot at
sentence end. Please see attached path for details.
--
assignee: docs@python
components: Documentation
files: urllib-typo-space-after-dot.patch
keywords
New submission from Vladimir Rutsky altsy...@gmail.com:
There is a typo in argparse module documentation:
The ``nargs`` keyword argument associates a different number of command-line
arguments with a single action.. (two dots at end).
Patch based on official http://svn.python.org/projects
New submission from Vladimir Rutsky altsy...@gmail.com:
In Python 2.7 and 3 branch at
http://svn.python.org/projects/python/branches/py3k/ file
Doc/library/argparse.rst has incorrectly formatted list at line 648:
* ``'store'`` - This just stores the argument's value. This is the default
New submission from Vladimir Rutsky altsy...@gmail.com:
There is missed dot at end of sentence in argparse module documentation. Please
see attached patch for details.
Patch based on official http://svn.python.org/projects/python/branches/py3k/
repository, but typo is also noted in Python 2.7
Vladimir Rutsky rutsky.vladi...@gmail.com added the comment:
SilentGhost, thanks for the patch! I can confirm, that adding os.path.normcase
fixes issues with different cases of files.
I believe there also may be issue with FAT's long file name mangling, like
C:\PROGRA~1\python26\ instead of C
Vladimir Rutsky rutsky.vladi...@gmail.com added the comment:
Sorry I was wrong - patch don't fix original issue.
Case should be normalized not only for directories provided through
--ignore-dir, but also for directories obtained from __file__. In my tests on
Windows Ignore.names(self
New submission from Vladimir Rutsky rutsky.vladi...@gmail.com:
This is code from recent trace.py
(http://svn.python.org/view/python/branches/release27-maint/Lib/trace.py?view=markup):
trace.py:169:
# Ignore a file when it contains one of the ignorable paths
for d in self._dirs
Changes by Vladimir Rutsky rutsky.vladi...@gmail.com:
Added file: http://bugs.python.org/file20369/test.cmd
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10896
Changes by Vladimir Rutsky rutsky.vladi...@gmail.com:
Added file: http://bugs.python.org/file20370/test.out
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10896
Vladimir Rutsky rutsky.vladi...@gmail.com added the comment:
Workaround for people on Windows who don't wan't to modify trace.py:
to get clean trace of only your project calls add to ignore list python path
with mix of character cases. For me worked out this string:
python -m trace --ignore
New submission from Vladimir Rutsky altsy...@gmail.com:
I think there is a typo in threading documentation:
In any situation where the size of the resource size is fixed,
you should use a bounded semaphore.
- size of the resource size, see attached patch for proposed fix.
(Based on official
29 matches
Mail list logo
