From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Iorga, Cristian" <cristian.iorga@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Developing hob/bitbake using PyDev
Date: Tue, 07 Aug 2012 10:13:04 +0100 [thread overview]
Message-ID: <1344330784.9756.213.camel@ted> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB161794D1@IRSMSX102.ger.corp.intel.com>
On Tue, 2012-08-07 at 07:48 +0000, Iorga, Cristian wrote:
> Remote debugging seems possible, but we did not set it up (yet).
>
> “Fix and Continue” we don’t know if it exists in Python world, because
> of the way Pyhon (interpreter + base language works).
>
> I.e.: Python: from module import spam
>
> spam will be initialized after this one.
>
> How Python will handle a reload or something similar in this case?
Python can reload modules but you'd have to deactive anything using them
to be able to reload so you'd have to reset all the state. I therefore
suspect this aspect would be hard.
> If anyone have any insights into this issues, please help me.
>
> P.S.: Doing remote debugging of hob seems to need changes in
> hob/bitbake sources, which I guess would not be acceptable to be
> integrated into main branch, isn’t it?
I'd not rule them out, particularly if how to use them was well
documented. We'd need something well thought out though for it to be
merged. It really depends on the kinds of changes needed and how
invasive they were.
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Iorga, Cristian" <cristian.iorga@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [poky] Developing hob/bitbake using PyDev
Date: Tue, 07 Aug 2012 10:13:04 +0100 [thread overview]
Message-ID: <1344330784.9756.213.camel@ted> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB161794D1@IRSMSX102.ger.corp.intel.com>
On Tue, 2012-08-07 at 07:48 +0000, Iorga, Cristian wrote:
> Remote debugging seems possible, but we did not set it up (yet).
>
> “Fix and Continue” we don’t know if it exists in Python world, because
> of the way Pyhon (interpreter + base language works).
>
> I.e.: Python: from module import spam
>
> spam will be initialized after this one.
>
> How Python will handle a reload or something similar in this case?
Python can reload modules but you'd have to deactive anything using them
to be able to reload so you'd have to reset all the state. I therefore
suspect this aspect would be hard.
> If anyone have any insights into this issues, please help me.
>
> P.S.: Doing remote debugging of hob seems to need changes in
> hob/bitbake sources, which I guess would not be acceptable to be
> integrated into main branch, isn’t it?
I'd not rule them out, particularly if how to use them was well
documented. We'd need something well thought out though for it to be
merged. It really depends on the kinds of changes needed and how
invasive they were.
Cheers,
Richard
next prev parent reply other threads:[~2012-08-07 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 7:48 Developing hob/bitbake using PyDev Iorga, Cristian
2012-08-07 9:13 ` Richard Purdie [this message]
2012-08-07 9:13 ` [poky] " Richard Purdie
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=1344330784.9756.213.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=cristian.iorga@intel.com \
--cc=poky@yoctoproject.org \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.