Improve Python 3 porting guide

[quozl]

After running 2to3, there is no other guidance. There may be common patterns of change that are required. These can be added to the guide.

@Aniket21mathur, as an opportunity.

[quozl]

It depends on experience in the task. Have you ported any Sugar activities to Python 3 yet? Do that first.

[Ritinikhil]

I will work on this issue .

[quozl]

Which activities will you port?

[Ritinikhil]

Subject: Inquiry Regarding Open Source Contribution in Sugar Labs Dear Mr. James Cameron, I trust this message finds you well. My name is Nikhil Singh, and I am an experienced Python developer with a background in working with various Python libraries on diverse projects. While I have gained proficiency in several aspects of Python development, venturing into open source contributions is a new endeavor for me. I recently came across Sugar Labs and am keen on contributing to the community. I am reaching out to seek guidance on how to initiate my open source contributions specifically within the realm of Python development for Sugar Labs. I appreciate your time and expertise and would be grateful for any assistance or advice you can provide to help me navigate the process of getting started with open source contributions in Sugar Labs. Thank you for your consideration. Best regards,

Nikhil Singh

Message ID: ***@***.***>

…

[chimosky]

@Ritinikhil a great place to start would be setting up a dev environment and do some Python 3 porting following the existing documentation before you can improve it.

[quozl]

G'day Nikil, thanks for your mail.

I asked which activities you would be porting because doing that porting is a pre-requisite for rewriting the guide to porting, and as far as I could tell you hadn't done any porting yet. You can identify activities for porting using the guide to porting, which says as one of the final steps;

• Change exec value in activity.info from sugar-activity to sugar-activity3

So all you have to do is find repositories or activities that contain sugar-activity as the exec value in their file activity.info, then iterate through that list to select which activity you'd like to port. A common method is to count the lines of source code and pick the smallest code base.

Keep in mind that not all activities are on GitHub for Sugar Labs. Some are in personal GItHub repositories. Some are ZIP files (*.xo) on download.sugarlabs.org, some are only on activities.sugarlabs.org, and if I recall correctly some are on the Wiki. Sugar Labs has a long history. Hope that helps!

[Ritinikhil]

Dear , I m facing this error "Cannot find reference 'Gtk' in '__init__.py'" while using from gi.repository import Gtk

…

On Tue, Feb 13, 2024 at 11:32 PM Ibiam Chihurumnaya < ***@***.***> wrote: @Ritinikhil <https://github.com/Ritinikhil> a great place to start would be setting up a dev environment <https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md> and do some Python 3 porting following the existing documentation <https://github.com/sugarlabs/sugar-docs/blob/master/src/python-porting-guide.md> before you can improve it. — Reply to this email directly, view it on GitHub <#184 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5YU43CRLQRTTHMWESCOFUDYTOTETAVCNFSM4IOAUMZ2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJUGIYTCNBWGA2A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[quozl]

Thanks. I don't think you have enough experience to start this task. I suggest you find another task.

However, given the error you mention, make sure you have a GObject typelib for Gtk 3.0, which on Ubuntu would usually be the package named gir1.2-gtk-3.0

What version of this package is installed on your system?