Call for papers is open till March 12

We look forward to seeing your proposals for PiterPy 2025!

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!

  • Hot Prod Python
    • Using Free-Threading Python, nogil and synchronization difficulties in production.
    • Python JIT for application acceleration.
    • Astral.sh and Python infrastructure in Rust.
    • Copilot and other AI assistants for Python development.
    • LLM Agents.
    • Complex layered applications.
  • Core Python
    • Python under the hood.
    • Basic Python concepts with simple examples.
    • CPython, PyPy, GraalPy, Cython, and other interpreters.
    • Subinterpreters and immutable data structures.
    • Language novelties.
    • Internals of the language elements.
  • 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).
    • Linters: code complexity, naming, object relationships, layers, etc.
    • Troubleshooting.
    • Python’s interaction with other technologies.
  • Libraries and tools
    • Python standard library.
    • Own and popular libraries and frameworks.
    • Advanced use of libraries (e.g. SQLAlchemy).
    • 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.
    • Best practices and work optimization.
  • Backend
    • Web frameworks.
    • Microservices architecture.
    • Development of internal and external APIs.
    • 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.
    • Helpful tools and design life hacks.
    • Extensive use of approaches for large applications in Python (e.g., CQRS, DDD).
  • Fundamentals
    • Back to Basics.
    • Ecosystem and new features overview.
    • Utilizing AI / Code Completion for enterprise level application development.
    • Development infrastructure.
    • Pythonic Way.
  • Other
    • Using Python in hardware.
    • GUI in Python.
    • Desktop application development.
    • Application of Python in solving scientific and non-standard problems, as well as in new fields.
    • Python and other languages: interop, performance, safety.
    • PyScript, running Python directly in HTML.

Archive

Check out what’s been happening at past PiterPy conferences

Watch

Submission process

  1. You submit a proposal

  2. +1–2 DAYS

    We contact you

  3. +5 DAYS

    You discuss your content with your PC member

  4. CONVENIENT TIME FOR YOU

    You have calls with PC, rehearse and prepare for your session

  5. March 12

    We close CFP

  6. March 25

    We let you know about our final decision

  7. CONVENIENT TIME FOR YOU

    We help you get your content ready for production

  8. May 16–17

    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 program@piterpy.com. Also, don’t forget to read the speaker’s memo.