On Tue, Dec 30, 2014 at 5:34 PM, Ian Kelly wrote:
> On Mon, Dec 29, 2014 at 7:05 PM, Chris Angelico wrote:
>> Are .pyc files compatible across revisions? Could I carry this file to
>> a 2.7.9 and see if the crash still happens?
>
> PEP 6 requires that .pyc files for a particular major release mus
On Mon, Dec 29, 2014 at 11:34 PM, Ian Kelly wrote:
> On Mon, Dec 29, 2014 at 7:05 PM, Chris Angelico wrote:
>> Are .pyc files compatible across revisions? Could I carry this file to
>> a 2.7.9 and see if the crash still happens?
>
> PEP 6 requires that .pyc files for a particular major release mu
On Mon, Dec 29, 2014 at 7:05 PM, Chris Angelico wrote:
> Are .pyc files compatible across revisions? Could I carry this file to
> a 2.7.9 and see if the crash still happens?
PEP 6 requires that .pyc files for a particular major release must
work with all the bug fix releases for that version.
--
On Tue, Dec 30, 2014 at 12:40 PM, Steven D'Aprano
wrote:
> Chris Angelico wrote:
>
>> Unlike playing with sre_constants.pyc, this one *does* result in a
>> different file after renaming away the .pyc. So somehow, SOMEHOW, the
>> .pyc file became corrupt. Is this something worth reporting? I now
>>
Chris Angelico wrote:
> Unlike playing with sre_constants.pyc, this one *does* result in a
> different file after renaming away the .pyc. So somehow, SOMEHOW, the
> .pyc file became corrupt. Is this something worth reporting? I now
> have what appears to be a file whose presence in the current dir
Chris Angelico wrote:
On Tue, Dec 30, 2014 at 7:17 AM, Ian Kelly wrote:
You could try renaming the .pyc instead of deleting it.
Hmm, and in doing so I just learned that they don't, after all, have
any sort of timestamp in them - I thought they did.
I think it contains the timestamp of the
On Tue, Dec 30, 2014 at 5:58 AM, Peter Otten <__pete...@web.de> wrote:
> OK. sre_constants.py looks pretty generic, the only module it imports (_sre)
> is a built-in and the interpreter is known-good. If the modules imported
> before sre_constants.py are known-good, too, and no other debian user se
On Tue, Dec 30, 2014 at 7:17 AM, Ian Kelly wrote:
> On Mon, Dec 29, 2014 at 9:28 AM, Chris Angelico wrote:
>> Why is sre_constants segfaulting?! It's such a simple file! I assume
>> the "matches" comment means it thinks there's no problem with the .pyc
>> file; is it possible that, despite those
On Mon, Dec 29, 2014 at 9:28 AM, Chris Angelico wrote:
> Why is sre_constants segfaulting?! It's such a simple file! I assume
> the "matches" comment means it thinks there's no problem with the .pyc
> file; is it possible that, despite those checks, there's an issue
> there? I could delete the .py
Chris Angelico wrote:
> On Tue, Dec 30, 2014 at 4:28 AM, Peter Otten <__pete...@web.de> wrote:
>> Maybe the interpreter itself is corrupted? Google suggests that debsums
>> may be the tool to find out.
>
> That's part of what I'm trying to track down, but why it should have
> changed in the past
On Tue, Dec 30, 2014 at 4:28 AM, Peter Otten <__pete...@web.de> wrote:
> Maybe the interpreter itself is corrupted? Google suggests that debsums may
> be the tool to find out.
That's part of what I'm trying to track down, but why it should have
changed in the past few days is beyond me. There's no
Chris Angelico wrote:
> On Tue, Dec 30, 2014 at 3:05 AM, Irmen de Jong
> wrote:
>> On 29-12-2014 15:33, Chris Angelico wrote:
>>
>>> So clearly an empty 'site' can be imported safely, but running Python
>>> without -S segfaults.
>>>
>>> Can anyone advise as to where I should look for the cause of
On Tue, Dec 30, 2014 at 3:05 AM, Irmen de Jong wrote:
> On 29-12-2014 15:33, Chris Angelico wrote:
>
>> So clearly an empty 'site' can be imported safely, but running Python
>> without -S segfaults.
>>
>> Can anyone advise as to where I should look for the cause of the trouble?
>>
>> ChrisA
>
> Pe
On Tue, Dec 30, 2014 at 2:57 AM, Dave Angel wrote:
> My gut feeling is you should check if there is another site.py* anywhere on
> your system. (Use find rather than just manually checking the sys.path
> locations)
I used imp.find_module and it showed the one in
/usr/lib/python2.7/site.py would
On 29-12-2014 15:33, Chris Angelico wrote:
> So clearly an empty 'site' can be imported safely, but running Python
> without -S segfaults.
>
> Can anyone advise as to where I should look for the cause of the trouble?
>
> ChrisA
Perhaps starting python with -v provides some more info on when exa
On 12/29/2014 09:33 AM, Chris Angelico wrote:
rosuav@sikorsky:~$ python -S
Python 2.7.3 (default, Mar 13 2014, 11:03:55)
[GCC 4.7.2] on linux2
rosuav@sikorsky:~$ python
Segmentation fault
This is the system Python on Debian Wheezy, and I haven't changed
site.py at all. This broke some time in
16 matches
Mail list logo
