Skip to content

Latest commit

 

History

History
70 lines (48 loc) · 3.61 KB

File metadata and controls

70 lines (48 loc) · 3.61 KB

Where to ask for help

Python Study Guide is maintained as a public educational project. Questions and reports should use the channel that matches their purpose.

Need Preferred channel
Ask about material already published in this repository Open a Learning question issue
Incorrect or broken repository content Open a Bug report issue
Suggest a new chapter, example, exercise, or improvement Open a Content suggestion issue
Correct or improve a translation Open a Translation improvement issue
Learn how to prepare a contribution Read the contribution guide
Report a security vulnerability Follow the security policy and report privately
Report harassment or other conduct concerns Follow the code of conduct and report privately

Issues may be written in English, Brazilian Portuguese, or Spanish. Keep repository paths, code, commands, and technical identifiers exactly as they appear.

What project support covers

Support may help with:

  • locating or understanding material published in this repository;
  • reproducing an example exactly as documented;
  • identifying errors, unclear explanations, or broken navigation;
  • understanding contribution requirements;
  • proposing focused improvements connected to the roadmap;
  • clarifying whether a request belongs in this repository.

What project support does not cover

This repository does not provide:

  • urgent, guaranteed, or private technical support;
  • completion of school, university, interview, or employment assignments on someone's behalf;
  • debugging of unrelated personal, employer, client, or proprietary projects;
  • credential recovery, account support, or support for GitHub, Python, OpenAI, or third-party products;
  • individualized mentoring with guaranteed response times;
  • legal, financial, medical, cybersecurity, or employment advice.

Questions about external products should be directed to their official support channels and documentation.

How to ask a useful question

A useful request normally includes:

  • the exact repository path or public URL;
  • what you are trying to understand or reproduce;
  • what you expected;
  • what happened instead;
  • a minimal safe example;
  • the Python version and operating system when execution is involved;
  • commands and checks already performed;
  • confirmation that private and proprietary information was removed.

Do not upload entire private projects when a small fictional example can demonstrate the same problem.

Response expectations

The project is maintained on a best-effort basis. Opening an issue does not guarantee a response time, implementation, or acceptance of the proposed solution.

Requests may be closed when they are outside the project scope, duplicate existing work, lack enough public information to evaluate, contain confidential material, or conflict with the project's educational and safety standards.

Respectful follow-up is welcome. Repeated pressure, unsolicited private messages, or attempts to bypass the public review process are not.