> For the complete documentation index, see [llms.txt](https://report.pytogo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://report.pytogo.org/report-pycon-togo-2026/conference-background/30-days-of-python.md).

# 30 Days of Python

<figure><img src="https://66880775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIw3e7P1KBIBjioWqRI38%2Fuploads%2F0OGaSFWTHUggX69ogXMm%2FJCE_0442.jpg?alt=media&amp;token=60502db6-d76d-48f1-89d7-f12b06d83587" alt=""><figcaption></figcaption></figure>

As part of the activities leading up to PyCon Togo 2026, Python Togo organized the **30 Days of Python** program, an online learning initiative designed to help participants learn Python ahead of the conference.

The program ran from June 1 to the end of June 2026, providing participants with an opportunity to develop their programming skills and build a foundation in Python before attending PyCon Togo.

The initiative attracted approximately 100 participants from multiple countries, with the majority joining from Togo. Of these participants, **72 successfully completed the program,** demonstrating their commitment to learning and developing their programming skills.

#### Participation Overview

* **Total participants:** Approximately 150
* **Program completers:** 72
* **Completion rate:** Approximately 50%
* **Countries represented:** Multiple countries, primarily Togo
* **Program duration:** July 1–31, 2026

#### Gender Representation

The program also provided an opportunity to assess gender representation in Python learning activities. Among participants, 19.4% were women and 80.6% were men.

* **Women:** 19.4%
* **Men:** 80.6%

These figures highlight the importance of continuing to encourage women's participation in programming and open-source communities.

<figure><img src="https://66880775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIw3e7P1KBIBjioWqRI38%2Fuploads%2FywBtnhuZdawaHfZjBVYO%2FScreenshot%20from%202026-10-14%2000-17-47.png?alt=media&amp;token=bf293ec3-ee98-44fe-a76c-27fa97224af8" alt=""><figcaption></figcaption></figure>

#### Impact and Objectives

The 30 Days of Python program aimed to prepare participants for PyCon Togo 2026 by introducing them to Python and helping them develop foundational programming skills before the conference.

By offering online learning opportunities, the program made it possible for people from different locations to participate, extending its reach beyond Togo and contributing to the development of a broader Python learning community.

The initiative formed part of Python Togo's wider commitment to promoting accessible programming education, supporting beginners, and encouraging continuous learning within the local and regional technology ecosystem.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://report.pytogo.org/report-pycon-togo-2026/conference-background/30-days-of-python.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
