> 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/pycon-togo-2025-post-conference-report/attendees-overview.md).

# Attendees Overview

<figure><img src="https://959432101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkBsSEYNEnJr8QOHzhnFi%2Fuploads%2Fr2rwTU4Inaoy2U07KltP%2FIMG_9616.jpg?alt=media&amp;token=d18076e3-f747-413a-acf0-575edc89095b" alt=""><figcaption></figcaption></figure>

### Highlights

PyCon Togo 2025 drew a diverse and motivated crowd: our 30 Days of Python challenge prepared hundreds for the conference, and the main event welcomed 250 in-person participants, with seamless integration of livestreamed sessions.

### Representation Overview

**Gender Distribution (In-Person)**

* Women: 30% (\~75)
* Men: 70% (\~175)

<figure><img src="https://959432101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkBsSEYNEnJr8QOHzhnFi%2Fuploads%2F7PYvKqPqabsC83Q10FYh%2Fimage.png?alt=media&amp;token=c5b7fbcb-89bb-4384-8793-c62782b82c93" alt=""><figcaption></figcaption></figure>

## Attendance Breakdown

**Breakdown of In-Person Attendees**

* Participants: 200
* Speakers & Contributors: 50

**Breakdown of online Attendees**

In addition to the participants present on site, PyCon Togo 2025 was followed online by hundreds viewers around the world.\
Togo accounted for the majority of the audience, followed by Nigeria, the United States, France, and the United Kingdom.\
This international audience demonstrated that, even for its first national edition, PyCon Togo already has a global reach.

<figure><img src="https://959432101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkBsSEYNEnJr8QOHzhnFi%2Fuploads%2FeHCRVbw4Forw4XqKqel5%2FScreenshot%20from%202025-09-08%2002-02-30.png?alt=media&amp;token=5becae83-1468-4fd7-81cb-e29b94633a13" alt=""><figcaption></figcaption></figure>

### Group Representation

The audience primarily consisted of Python beginners, supported by speakers and core contributors who guided and facilitated sessions. This mix ensured a dynamic learning atmosphere and strong mentor-learner engagement.

* **Beginners:**\
  Many attendees joined the conference after participating in the **30 Days of Fighters Challenge**, which allowed non-developers to gain skills and get familiar with Python before the event.
* **Intermediate:**\
  Developers with practical Python experience deepened their knowledge through workshops and technical sessions.
* **Experts:**\
  Experienced professionals shared their expertise in advanced talks, enhancing the quality of discussions.
* **Local Companies and Partners:**\
  The event was supported by **two local companies** and **two local partners**, contributing to its success and local impact.
* **Local Python Communities:**\
  User groups and coding clubs actively participated, bringing local perspectives and enriching conversations.
* **Students and Researchers:**\
  Many students and researchers attended the conference, engaging in learning and networking.
* **Industry Professionals:**\
  Representatives from tech companies explored opportunities for collaboration and growth within the Python ecosystem.

This diversity fostered meaningful interactions, strengthening the Python community in Togo and across West Africa.


---

# 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/pycon-togo-2025-post-conference-report/attendees-overview.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.