Start of main content

The call for papers is closed

We will be glad to see your applications for PiterPy 2024! Stay tuned for updates.

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!

  • Vanilla Python
    • Performance and optimization. Code acceleration, profiling, debugging, and optimization tricks such as improving loop execution time and handling big data.
    • CPython and other interpreters. Features and internals of CPython, PyPy, Jython (is it alive?) and how to use them in different situations.
    • "Back to Basics. Basic Python concepts explained with simple examples. For example, the __slots__ mechanism for saving memory and solving hash collisions in dictionaries, asynchrony in details and errors, etc.
    • The Pythonic Way. Basic principles, tips for turning bad code into good code, examples of the Pythonic approach to solving tasks.
    • Python Standard Library. Facilities, examples of use, features and interesting details.
    • Proprietary libraries and frameworks. Difficulties of development, developers' experiences and best practices.
    • Python under the hood. Interpreter implementation details: GIL, async, how dict works.
    • Developer tools. Linters, batch managers, etc.
  • Python testing
    • Basic testing concepts. Unit testing (and when is it unnecessary?), integration and functional testing, and their application to Python. What a developer needs to know to be comfortable.
    • Libraries and tools. Overview of popular libraries and tools for testing: unittest, pytest, nose and others. Their features and best practices.
    • Test-driven development (TDD) in Python. The process of writing tests before implementing functionality.
    • Testing web applications in Python. Application of tools and approaches such as Selenium, Django Testing Framework and Flask Testing.
    • Performance Testing. Tools and techniques for measuring and optimizing the performance of Python applications. Profiling, stress testing and load testing.
    • Testing asynchronous code. Features of asynchronous code testing in Python, using asyncio, Trio, Quart and other libraries.
  • ML/MLOps
    • Python-based MLOps tools. Exploiting, completing, and comparing tools such as Airflow, MLFlow, DVC, etc.
    • ML libraries in Python. Useful libraries, their operation, and related problems
    • Deploying ML models using Python. Ways to deploy models. Schedule batch processing, microservices, working with queues
  • Backend
    • Monolithic application development
    • Web frameworks
    • Microservice architecture
    • Internal and external API development
    • Asynchronous programming
    • ORM, databases and interaction with them
    • Web application caching and optimization
    • Observability: logging, monitoring and tracing
    • Application configuration
  • Security
    • Vulnerabilities in popular Python libraries.
    • Web application vulnerabilities, OWASP.
    • Supply chain dependency attacks.
    • Using Python tools to find vulnerabilities.
    • Fuzzing.
  • Other
    • Using Python in hardware. Embedded devices, IoT, robotics, etc.
    • GUI in Python. PyQt, Kiwi, Tkinter, etc.
    • Desktop application development.
    • Bioinformatics, astronomy, astrophysics, and other sciences. Talks on applications of Python to scientific problems
    • Exotic problems and applications of Python. Demoscenes, sizecoding, quine


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. July 15

    We close CFP

  6. July 31

    We let you know about our final decision

  7. Convenient time for you

    We help you get your content ready for production

  8. November 7 (online), 13-14 (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.

  • Technical expertise

    You have experience and have completed projects in the field in question. The topic of your presentation is technically 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 technical 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.