Yaroslav Halchenko added the comment:
Might (although unlikely) be related to https://bugs.python.org/issue40634
which is about BlockingIOError being raised (and ignored) if SelectorEventLoop
is reused (not the case here) also in the case of short lived processes.
--
nosy
Yaroslav Halchenko added the comment:
any feedback/ideas/fixes would still be highly appreciated. Thank you!
--
___
Python tracker
<https://bugs.python.org/issue40
New submission from Yaroslav Halchenko :
This is a reincarnation of previous issues such as
- older https://bugs.python.org/issue21595 which partially (with ack on that)
addressed the issue awhile back
- more recent https://bugs.python.org/issue38104 which was closed as "wont fix&qu
Yaroslav Halchenko added the comment:
FWIW, our more complete test filename is
# python3 -c 'import patoolib.util as ut; print(ut.guess_mime(r" \"\`;b
|.tar.gz"))'
(None, None)
which works fine with older versions
--
___
Python
New submission from Yaroslav Halchenko :
Our tests in DataLad started to fail while building on Debian with Python
3.7.5rc1 whenever they passed just fine previously with 3.7.3rc1. Analysis
boiled down to mimetypes
$> ./python3.9 -c 'import mimetypes; mimedb =
mimetypes.MimeTypes(str
Yaroslav Halchenko <yarikop...@gmail.com> added the comment:
I have spent too much time in Python to be able to compare to other languages
;) but anywhere I saw RNG being used, there was a way to seed it or to provide
a state. tempfile provides no such API
my usecase -- comparison o
New submission from Yaroslav Halchenko <yarikop...@gmail.com>:
It is quite often desired to reproduce the same failure identically. In many
cases sufficient to seed the shared random._inst (via random.seed). tempfile
creates new instance(s) for its own operation and does not provi
Yaroslav Halchenko <yarikop...@gmail.com> added the comment:
Thank you for the follow-ups!
Wouldn't it be better if Python documentation said exactly that
On Linux, write() (and similar system calls) will transfer at most 0x7000
(2,147,479,552) bytes, returning the number of
New submission from Yaroslav Halchenko <yarikop...@gmail.com>:
originally detected on python 2.7, but replicated with python 3.5.3 --
apparently io.FileIO, if given a bytestring of 2GB or more, cannot write it all
at once -- saves (and returns that size) only 2GB - 4096.
I found no indi
Changes by Yaroslav Halchenko <yarikop...@gmail.com>:
--
title: tarfile would fail to extract tarballs with files under R/O directories
-> tarfile would fail to extract tarballs with files under R/O directories
(twice)
___
Python tra
Yaroslav Halchenko added the comment:
Dear Catherine,
Thank you very much for looking into it!! And sorry that I have missed the fact
of recursive addition when pointing to a directory. Indeed though, tar handles
that case a bit more gracefully.
BUT I feel somewhat dumb since I am afraid
New submission from Yaroslav Halchenko:
If tarfile contains a file under a directory which has no write permission,
extractall would fail since chmod'ing of the directory is done right when it is
"extracted".
Please find attached a quick script to demonstrate the problem using
P
Yaroslav Halchenko added the comment:
the function getargspec was removed but references to it within docstrings
remained:
$ git grep getargspec
Doc/library/inspect.rst: The first four items in the tuple correspond to
:func:`getargspec`.
Doc/library/inspect.rst: :func:`getargspec
Changes by Yaroslav Halchenko yarikop...@gmail.com:
--
nosy: -Yaroslav.Halchenko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16997
New submission from Yaroslav Halchenko yarikop...@gmail.com:
We ran into this while generating documentation for our project (PyMVPA) with
recent sphinx and python2.6 (fine with 2.5, failed for 2.6, 2.7, 3.1), which
relies on traversing all attributes given by dir(obj), BUT apparently
Yaroslav Halchenko yarikop...@gmail.com added the comment:
yikes... surprising resolution -- I expected that fix would either makes
__abstractmethods__ accessible in derived types or becomes absent from output
of dir() -- but none of those has happened. Now we ended up with a consistent
non
New submission from Yaroslav Halchenko yarikop...@gmail.com:
as you can see from below, sys. is used, but never imported (besides a
docstring)
$ git describe
upstream/0.5.0.dev-875-gf06319e
$ grep -5 'sys' /home/yoh/proj/misc/python/Tools/gdb/libpython.py
During development, I've been
Yaroslav Halchenko yarikop...@gmail.com added the comment:
sorry -- git describe was by mistake in there... report is based on SVN
revision 82502
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9235
Yaroslav Halchenko yarikop...@gmail.com added the comment:
Hi Nick,
Am I reading your right, Are you suggesting to implement this
manual looping/collecting/reporting separately in every unittest
which needs that?
On Tue, 11 May 2010, Nick Coghlan wrote:
Nick Coghlan ncogh...@gmail.com added
Yaroslav Halchenko yarikop...@gmail.com added the comment:
Fernando, I agree... somewhat ;-)
At some point (whenever everything works fine and no unittests fail) I wanted
to merry sweepargs to nose and make it spit out a dot (or animate a spinning
wheel ;)) for every passed unittest, so
Yaroslav Halchenko yarikop...@gmail.com added the comment:
In PyMVPA we have our little decorator as an alternative to Fernando's
generators, and which is closer, I think, to what Michael was wishing for:
@sweepargs
http://github.com/yarikoptic/PyMVPA/blob/master/mvpa/testing/sweepargs.py
NB
21 matches
Mail list logo
