[Sugar-devel] [Sugar emulator][Ubuntu 11.04] I can't install an activity (with the setup.py)

[James Simmons]

Laurent,

My advice was based on my experience with Fedora.  Based on what you're
seeing it would make sense to uninstall Canonical's Sugar (since it seems
to have the same issue with not having the sugar libraries in the
PYTHONPATH that Sweets does) and give Sweets another try.  It sounds like
with Sweets you don't need to use sugar.py in your Activity.  You might
still need to provide one for your XO bundle.  Maybe Aleksey can clear that
up.

You don't really need these libraries available outside of Sugar for
development, other than when running setup.py.  If using the sweets command
instead of setup.py gives the same result then your problems running my
examples should be solved.

Aleksey has a better knowledge of how Sugar runs under the hood, so his
advice will be better than mine.

Good luck,

James Simmons


On Mon, Dec 5, 2011 at 4:55 PM, laurent bernabe
<laurent.bernabe at gmail.com>wrote:

> Ok, Thanks. As James Simons advised me, I uninstalled Sweet distribution
> from my linux system.
>
> I would like to make the standard sugar emulator (this wich is given by
> Canonical) to work with Pippy, and to work with activities setup.py
>
> But it seems that many things are still to set ...
>
>
> 2011/12/5 Aleksey Lim <alsroot at activitycentral.org>
>
>> On Mon, Dec 05, 2011 at 06:28:15PM +0100, laurent bernabe wrote:
>> > Hello everyone,
>> >
>> > I am following the ActivitiesGuideSugar pdf from august 2010.
>> >
>> >
>> >    - I've fetched tutorial source code for etext activity (chapter 5 :
>> >    inheriting from Activity.activity)
>> >    - I've modified, carefully i think, the svg picture with Inkscape and
>> >    edited the xml structure
>> >    - I installed the Sugar Sweets distribution
>> >
>> > But when I try to setup the activity from the emulator terminal, I get
>> an
>> > error saying that there is no module called sugar.activity
>> > (the line in fault : "from sugar.activity import bundlebuilder".
>> >
>> > Have I forgotten an important step in my sugar environment ?
>>
>> The downside of using Sweets Distribution (and Sweets) is that you are
>> getting all libraries enabled only being in Sugar session. If you are
>> not in Sugar, the most useful setup.py's command are duplicated in
>> sweets command, e.g.:
>>
>>    sweets dist_xo
>>    sweets dist_source
>>    sweets genpot
>>
>> --
>> Aleksey
>>
>
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20111205/ef6dc812/attachment.html>