On 22.11.2016 18:03, Antoine Pitrou wrote:
You'll have to investigate yourself. First enable core dumps ("ulimit
-c unlimited"), then run gdb on the resulting core dump.
(or run Python directly under gdb)
It's seems indeed not to be a Problem with 3.6. I now have it with
newer 3.5 builds,
On Wed, Nov 23, 2016 at 6:20 AM, Victor Stinner
wrote:
> It's not bug but a feature :-) Python doesn't protect yourself against
> mistakes :-)
AIUI the normal way to protect yourself is to unlink (remove) the file
and create it from scratch, rather than truncate it.
ChrisA
__
It's not bug but a feature :-) Python doesn't protect yourself against
mistakes :-)
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-
On Nov 22, 2016, at 06:52, Stefan Scherfke
wrote:
> /tmp/py36/bin/python
In addition to the other comments, I'd check whether the new python is built
with --enable-shared. If so, it's probably not a good idea to be writing to
its library while running whereas, if it's not a shared build, it m
On Wed, Nov 23, 2016 at 1:00 AM, Stefan Scherfke
wrote:
>
>
> On 22.11.2016 12:52, Stefan Scherfke wrote:
>>
>>
>> Here is a minimal example that reproduces the error:
>>
>> $ /tmp/py36/bin/python
>> Python 3.6.0b4 (default, Nov 22 2016, 10:32:29)
>> [GCC 6.2.1 20160916 (Red Hat 6.2.1-2)] on linux
On Tue, 22 Nov 2016 12:52:59 +0100
Stefan Scherfke wrote:
> Hi all,
>
> I am trying to build a custom Conda installer for Python 3.6.0b4.
>
> I could successfully build an run Python. However, when I run
> the generated Conda installer, it dies with a "Bus error".
>
> It happens when Conda's m
On 22.11.2016 12:52, Stefan Scherfke wrote:
Here is a minimal example that reproduces the error:
$ /tmp/py36/bin/python
Python 3.6.0b4 (default, Nov 22 2016, 10:32:29)
[GCC 6.2.1 20160916 (Red Hat 6.2.1-2)] on linux
path = '/tmp/py36/lib/libpython3.6m.so.1.0'
f = open(path, 'wb')
BusError
