Call for papers is closed

Applications for PiterPy 2024 are closed. We will be glad to see your applications at the next conference!

Personal account of the speaker

Instant access to all your proposals. You may track their workflow and edit them in your personal account.

Sign in

We are interested in the following topics

If you have an interesting idea on a topic that is not on the list we will be happy to consider your proposal anyway!

  • Core Python
    • Python under the hood.
    • Basic Python concepts with simple examples.
    • CPython, PyPy, GraalPy, Cython, and other interpreters.
    • Subinterpreters and immutable data structures.
  • Development practices
    • Clean code, SOLID. Practices of "correct" OOP.
    • Not OOP alone: functional and other approaches to code writing.
    • Code review.
    • Approaches to development and branching in CVS (Trunk-Based Development).
  • Libraries and tools
    • Python standard library.
    • Own and popular libraries and frameworks.
    • Developer tools.
    • Performance and optimisation.
  • Testing and security
    • Basic concepts of testing in Python.
    • Libraries and tools for testing.
    • Testing web applications in Python.
    • Performance testing.
    • Testing asynchronous code in Python.
    • Security testing and vulnerability analysis of Python applications.
    • Secure development: technologies, tools and practices.
  • Backend
    • Web frameworks.
    • Microservices architecture.
    • Development of internal and external APIs.
    • Asynchronous programming.
    • ORM, databases and interaction with them.
    • Web application caching and optimisation.
    • Observability: logging, monitoring and tracing.
    • Application configuration.
    • Django's ecosystem.
    • Solving ML/DS/data engineering application problems.
  • Architecture and patterns
    • Different architectural approaches and patterns in practice.
    • System architecture basics for developers.
    • Architecture types.
    • Design and development approaches.
    • Commonly known patterns and design patterns in solving real-world problems.
    • Architecture Security.
    • Helpful tools and design life hacks.
  • Other
    • Using Python in hardware.
    • GUI in Python.
    • Desktop application development.
    • Application of Python in solving scientific and non-standard problems.
    • Python and other languages: interop, performance, safety.
  • Fundamentals
    • Back to Basics.
    • Ecosystem overview.
    • Using AI for application development.
    • Development infrastructure.
    • Career path of a Python developer.
    • Pythonic Way.


Check out what’s been happening at past PiterPy conferences


Submission process

  1. You submit your proposal

  2. + 2-3 days

    We contact you

  3. + 7 days

    You discuss your content with your PC member

  4. Convenient time for you

    You rehearse and prepare for your session

  5. June 18

    We close CFP

  6. July 9

    We let you know about our final decision

  7. Convenient time for you

    We help you get your content ready for production

  8. September 18 (online) and September 26-27 (offline)

    You give your session at the conference

Program committee

Each proposal will be examined by at least three reviewers from the Program Committee.

Selection process

  • Relevance

    You are going to discuss things that participants of the conference find useful not only yesterday but also today and in the future. In addition, the topic of your session matches the theme of the conference, and the content you are going to present matches the stated description.

  • Depth

    Your talk reveals the subject deeply and comprehensively. There is no need to talk about yet another Hello World (unless you think it’s a new, not widely known, but very promising technology).

  • Speaking experience

    If you have experience in speaking at conferences and meetups, this will be a great advantage. If this is your first presentation, be prepared to rehearse and practice.

  • Practical applicability

    The content is important from a practical point of view and you not only cover the existing problems / solutions, but also share your experience.

  • Expertise

    You have experience and have completed projects in the field in question. The topic of your presentation is sound. You have a good understanding of what you are talking about and have been involved in the implementation of the project you are describing.

  • Originality

    There is novelty in your session; the content either hasn’t been published before or presents a well-known topic / problem in a different light.

Additional information

  • If you are submitting on behalf of another person, please fill the form using the speaker’s contact information. You can leave your contacts in the last form field (the one which asks about a co-speaker or comments).

  • If you feel like you need help to prepare your session you can count on us: we can appoint a personal curator who will review your material and organize rehearsals.

  • Usually, we contact applicants within a week after the submission. If that hasn’t happened, feel free to contact us via email at Also, don’t forget to read the speaker’s memo.