> 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/our-global-audience.md).
# Our Global Audience
PyCon Togo 2025 brought together a **diverse audience** from multiple countries, reflecting the growing Python community across West Africa and beyond. The conference was attended by participants from at least **five African countries**:
* **Togo** (majority of attendees)
* **Nigeria**
* **Ghana**
* **Benin**
* **Côte d’Ivoire**
* **Morocco**
In addition to the African representation, we also had **international speakers** from:
* **United States**
* **France**
The attendees included a mix of **students, professionals, and non-tech participants**, representing a wide range of skill levels from beginners to experts.
The conference was **hybrid**, with both in-person and online participation. More than **250 participants attended in-person**, while the **live stream attracted over +200 viewers**, allowing people from around the world to engage with the sessions.
A large number of **photos were taken** during the in-person sessions, capturing the energy and engagement of the event. The full live stream and images are available for reference to showcase the **scope and impact of PyCon Togo 2025**.
## Online Audience by Country
---
# 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/our-global-audience.md?ask=&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.
