Holger Waldmann added the comment:
I am looking forward for this to be included.
My main use case is on restricted IoT devices, where I need to handle BLOBs of
2MB size.
As this is larger than my available RAM, I store need to store them in the
filesystem today.
This is ugly because it is
New submission from holger :
I intended to use the asyncio framework for building an end-to-end test for our
software. In the test I would spawn somewhere between 5k to 10k processes and
have the same number of sockets to manage.
When I built a prototype I ran into some scaling issues
holger added the comment:
Could you please tell me which exact posix document and paragraph says that?
In Linux sending can fail but once sendmsg worked the message is enqueued on
the other socket
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/unix/af_unix.c?id
New submission from holger :
The current implementation verifies that the sock passed is a stream socket.
This limitation appears to be arbitrary and is limiting.
* An AF_UNIX SOCK_DGRAM server socket becomes readable when one can accept(2)
it. Just like SOCK_STREAM.
* One could provide a
Holger Waldmann added the comment:
On Python 3.3.3 it is even worse.
I am using Python 3.3.3 (32bit) on Windows 7 (64bit).
Visual Studio C++ 2008 Express Edition is properly installed.
Note: I use Python 32bit because Visual Studio C++ 2008 Express Edition
includes only the 32bit compiler
holger krekel added the comment:
On Sun, Feb 10, 2013 at 12:43 PM, Nick Coghlan wrote:
>
> Nick Coghlan added the comment:
>
> You can use subtests to build parameterized tests, you can't use
> parameterized tests to build subtests.
I doubt you can implement parametrize
holger krekel added the comment:
On Sun, Feb 10, 2013 at 12:41 PM, Antoine Pitrou wrote:
>
> Antoine Pitrou added the comment:
>
> > Please don't commit I think we still need a discussion as to whether
> > subtests or paramaterized tests are a better approach. I ce
Holger Mickler added the comment:
I just stumbled upon the same problem with Python 2.7.3 on SLES 11 SP1 amd64.
Obviously, SuSE puts the needed header file into /usr/include/ncurses/, and one
can either create a symlink in /usr/include/ or apply a patch to
_curses_panel.c:
--- Modules
New submission from Holger :
Downloaded Python-3.2.2.tar
cd Python-3.2.2
./configure
make
Fail on:
.
ranlib libpython3.2m.a
make: *** No rule to make target `libpython3.2m.dll.a', needed by `python.exe'.
Stop.
libpython3.2m.a
Changes by holger krekel :
--
nosy: +hpk
___
Python tracker
<http://bugs.python.org/issue7897>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
New submission from holger krekel :
Seems like pypi.python.org does not properly maintain download counters
anymore, at least for a few packages i looked at like pytest,execnet,tox,nose.
--
components: None
messages: 148447
nosy: hpk
priority: normal
severity: normal
status: open
title
holger krekel added the comment:
Michael, if you have it i'd like to see the original post/concrete use case.
thanks, holger
--
___
Python tracker
<http://bugs.python.org/is
holger krekel added the comment:
FWIW i tend to agree and would probably prefer setup/teardown to result in an
error rather than be subsumed in an expected-to-fail marked test. I guess if
one regards setup/teardown as a place to implement pre/post-conditions than the
changes suggested by
Changes by holger krekel :
--
nosy: +hpk
___
Python tracker
<http://bugs.python.org/issue10548>
___
___
Python-bugs-list mailing list
Unsubscribe:
Holger Joukl added the comment:
> Holger, sorry your work has to be rejected.
No harm done - kind of paradoxical that my employer allowed me to release the
code into the wild but hasn't been willing to let me sign the contribution
form, in 4 years.
So it's at least out in the o
holger krekel added the comment:
Seems the inspect.getsourcefile regression now is in the RC1 of Python2.7 as
well. I suggest to apply the "getsourcefile.patch" patch which was attached
from David. I tested it and it works fine for Python2.7 and Python3.1.
--
st
holger krekel added the comment:
Great. Also to be backported to 2.x?
holger
On Fri, May 21, 2010 at 11:32 PM, Benjamin Peterson
wrote:
>
> Benjamin Peterson added the comment:
>
> Fixed in r81432 by making linecache smarter.
>
> --
> nosy: +benjamin.peterson
&g
New submission from holger krekel :
Executing the attached "inspect_failure.py" under python2.6 or python3.1
results in an assertion error: Python fails to obtain the source code of a
function that is defined at the end of a module whose last line does not
contain a line ending
holger krekel added the comment:
Well, maybe we could introduce a "linecache.setlines" function to give
the linecache module control over its internal caching and data
handling. What do you think?
--
___
Python tracker
<http://bu
holger krekel added the comment:
David, your getsourcefile.patch looks fine (and better than mine) to me.
--
___
Python tracker
<http://bugs.python.org/issue8
holger krekel added the comment:
Thanks for helping with this! Attached is a patch that adds a keyword
"check=True" to getsourcefile so that findsource can defer existence-checking
until after cache lookup. Eventually, findsource will still raise an IOError
if it can't find
New submission from holger krekel :
Somewhere between python 3.0.1 and 3.1.2 the behaviour of inspect.findsource
changed: it does not find the source code anymore for a code object whose
filename/source is in the linecache.cache because instead of the previous::
file = getsourcefile
Changes by holger krekel :
--
nosy: +hpk
___
Python tracker
<http://bugs.python.org/issue8564>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
holger krekel added the comment:
FWIW checking if an imported module really comes from a certain location and
erroring out is also how py.test does it.
--
nosy: +hpk
___
Python tracker
<http://bugs.python.org/issue8
holger krekel added the comment:
Ah, thanks for the pointer. So indeed, for me truncate(0)+seek(0)
works fine for all interpreters i care for (python2.4 - 3.1.X),
previously truncate(0) was enough.
--
___
Python tracker
<http://bugs.python.
New submission from holger krekel :
Running the attached file with python3.1.1 works fine, all assertions pass.
Running it with 3.1.2 gives me this output:
$ python3.1.2/bin/python3.1 stringio_fail.py
Traceback (most recent call last):
File "stringio_fail.py", line 12, in
holger krekel added the comment:
Actually py.test catches stdout separately for setup and for the test
code. Moreover, functional or integration test code (py.test is not
only for unittests) can easily trigger some implicit logging-module
usage which cannot eaysily be factored into a testcase
holger krekel added the comment:
To recap the use case: stdout is redirected during a test function run
which might trigger arbitrary usage of logging-functionality. Not
closing the temporary file would mean that there could be as many open
files as there are test functions - or one needs to
holger krekel added the comment:
I think the issue is unrelated to py.test - it just presents a use case
as it wants to run 1000's of tests and capture stdout/stderr per each
test function, cannot guess about a test's logging-usage yet wants to
minimize memory/resource usage and
29 matches
Mail list logo
