Not that would cause much of a slowdown, or that this would handle the
(hopefully unlikely) case where Python gains modules named identically
to Activity ones, but:
What are we trying to solve here? Are activities bundling third-party
Python libraries which have to be preferred in most cases over
system-provided ones (if present)?
Wouldn't it be better to ensure Activity developers make proper use of
namespaces when developing them instead?
On 2/6/2011 5:58 PM, Bernie Innocenti wrote:
On Sun, 2011-02-06 at 00:50 +0000, Aleksey Lim wrote:
Otherwise it is possible to include, eg, system modules before local ones.
Seems like a good idea.
Reviewed-by: Bernie Innocenti<ber...@codewiz.org>
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
