From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Python optimization
Date: Wed, 30 Mar 2011 18:16:51 -0400 [thread overview]
Message-ID: <4D93ABD3.1020707@balister.org> (raw)
Looks like we build python with the default setting of Optimize.
According to the patch we can opt-out of optimizing, any idea how to do
that?
I have some python that uses assert and docutils and they are not
running with python built this way? Is it really worth building python
this way?
Philip
reply other threads:[~2011-03-30 22:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D93ABD3.1020707@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox