This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author refi64
Recipients chaselton, ethan.furman, freakboy3742, mpaolini, r.david.murray, refi64, tritium
Date 2015-07-25.17:38:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <446A5187-4E7F-419D-B231-C3BD6B9BEEC9@gmail.com>
In-reply-to <1437825370.35.0.738920240552.issue23496@psf.upfronthosting.co.za>
Content
So...I have *no* clue why _struct can't be found.

Can you use gdb to get the segfault backtrace like you did before?

On July 25, 2015 6:56:10 AM CDT, Cyd Haselton <report@bugs.python.org> wrote:
>
>Cyd Haselton added the comment:
>
>I assume so; I'm using whatever is pulled frommy fork of the git repo.
>
>I've actually run into a different error that occured when i rebuilt to
>include readline support; when I run ./python -m test I;m getting
>"ImportError: no module named _struct found."
>
>Trying to figure that one out first...
>
>----------
>
>_______________________________________
>Python tracker <report@bugs.python.org>
><http://bugs.python.org/issue23496>
>_______________________________________
History
Date User Action Args
2015-07-25 17:38:24refi64setrecipients: + refi64, r.david.murray, freakboy3742, ethan.furman, mpaolini, chaselton, tritium
2015-07-25 17:38:24refi64linkissue23496 messages
2015-07-25 17:38:24refi64create