[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH] Don't lazily import the signal module

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Jeremy Katz <katzj@xxxxxxxxxx>
Date: Wed, 06 Sep 2006 09:28:07 -0400
Delivery-date: Wed, 06 Sep 2006 06:28:35 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Lazy imports are a quick way to cause a traceback, especially when code
starts being moved around or copied elsewhere.

Signed-off-by: Jeremy Katz <katzj@xxxxxxxxxx>

Attachment: xen-no-lazy-import.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH] Don't lazily import the signal module
  - From: Steven Smith

Prev by Date: [XenPPC] should vcpu_pause()/vcpu_sleep_nosync() give up?
Next by Date: Re: [Xen-devel] summagraphics on windows?
Previous by thread: [XenPPC] should vcpu_pause()/vcpu_sleep_nosync() give up?
Next by thread: Re: [Xen-devel] [PATCH] Don't lazily import the signal module
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.