[Sugar-devel] Toolkit Installation Sugar v0.113
James Cameron
quozl at laptop.org
Wed May 15 04:19:13 EDT 2019
Thanks!
I've proposed a pull request to let the caller specify the Python
version, and a draft pull request documenting how to build for both
versions.
https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/411
https://github.com/sugarlabs/sugar/pull/829
Aniket, when you say v0.113 this means you are using either git tag
v0.113 (i.e. e30b73f) or tarball. Seems unlikely you are doing that,
but instead you would be using HEAD of master branch instead. Is my
guess right?
Regarding the segmentation fault, please check
.sugar/default/logs/shell.log for any details, or run within gdb and
capture a backtrace of all threads.
On Wed, May 15, 2019 at 01:31:23PM +0530, ANIKET MATHUR wrote:
> Regards,
> I agree with, James. What I think is that since [1]this pr is not yet merged
> into master, sugar requires python 2,
> and the way I was installing Sugar builds the toolkit for Python 3. So I first
> installed Sugar from sucrose and then installed the toolkit-gtk3 v0.113 by
> hand.
> Doing this I am able to test ported activities through the command line using
> Ubuntu 18.04 terminal, but opening Sugar home view causes "Segmentation fault"
> with a warning "python2.7 has stopped unexpectedly". I am not yet able to
> figure out the reason for this.
>
> Regarding the Python version in [2]configure.ac, I think that the caller should
> be allowed to specify the version or alternatively since we are porting to six,
> a method building for both python2 and python3 would be great.
>
> I don't expect myself to be 100 percent right and expect to be corrected
> wherever required.
>
> Thanks a lot, everyone. ☺
>
> On Wed, May 15, 2019 at 3:17 AM James Cameron <[3]quozl at laptop.org> wrote:
>
> G'day Aniket,
>
> If you were using the native sugar build method, then you are using
> HEAD, which contains all patches since 0.113. Don't try to apply the
> patch that Alex pointed out, as it is already applied.
>
> The error message "ImportError: No module named sugar3" is caused by
> not installing the Toolkit for Python 2.
>
> Sugar 0.113 requires Python 2.
>
> Toolkit by default installs for Python 3.
>
> You can verify this is the situation by testing the import by hand
> using different versions of Python;
>
> python3 -c 'import sugar3' # expect pass
>
> python2 -c 'import sugar3' # expect fail
>
> You'll find in [4]configure.ac where the Python version is chosen.
>
> [5]https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac
> #L18
>
> Perhaps that line should allow the caller to specify the version.
>
> What do you think?
>
> On Tue, May 14, 2019 at 04:42:16PM +0530, ANIKET MATHUR wrote:
> > Greetings everyone,
> >
> > I was installing Sugar v0.113 using the Native Sugar build method [1]
> here. I
> > was using Ubuntu 18.10. After installation, on running Sugar I received
> the
> > error message "ImportError: No module named sugar3". Need help with a
> couple of
> > questions
> > 1) Is there a need to have a build of the older version for v0.113 to
> work
> > properly?
> > (never paid attention to that before).
> > 2) What is the correct procedure for installing v0.113?
> > Thanks!
> >
> > References:
> >
> > [1] [6]https://github.com/sugarlabs/sugar/blob/master/docs/
> development-environment.md
>
> > _______________________________________________
> > Sugar-devel mailing list
> > [7]Sugar-devel at lists.sugarlabs.org
> > [8]http://lists.sugarlabs.org/listinfo/sugar-devel
>
> --
> James Cameron
> [9]http://quozl.netrek.org/
>
> References:
>
> [1] https://github.com/sugarlabs/sugar/pull/805
> [2] http://configure.ac/
> [3] mailto:quozl at laptop.org
> [4] http://configure.ac/
> [5] https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/configure.ac#L18
> [6] https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md
> [7] mailto:Sugar-devel at lists.sugarlabs.org
> [8] http://lists.sugarlabs.org/listinfo/sugar-devel
> [9] http://quozl.netrek.org/
--
James Cameron
http://quozl.netrek.org/
More information about the Sugar-devel
mailing list