Pyproject.toml: The modern Python project definition file, explained

แชร์
ฝัง
  • เผยแพร่เมื่อ 5 พ.ย. 2024

ความคิดเห็น • 17

  • @ВладимирКирюшин-г5ъ
    @ВладимирКирюшин-г5ъ 7 หลายเดือนก่อน +6

    Thanks! I've been using an older setup.py approach, but I found pyproject.toml much more convenient.

  • @felipealvarez1982
    @felipealvarez1982 8 หลายเดือนก่อน +4

    Very useful for newbs like me, to do things following best practices. Thanks

  • @davidpaez_co
    @davidpaez_co 5 หลายเดือนก่อน +2

    This was an excellent explanation. Thank you so much Serdar!

  • @ayeameen
    @ayeameen ปีที่แล้ว +3

    Thanks so much for such a concise introduction!

  • @pawjast
    @pawjast 2 หลายเดือนก่อน +1

    Great explanation - just what I needed!

  • @tascsolutions6483
    @tascsolutions6483 6 หลายเดือนก่อน +1

    Thanks, you helped explain things as I have been trying out poetry in my new apps. Curious if you use it. I find it cumbersome up front but will keep using to see if more usage will streamline things. Where exactly does your .egg folder reside?

    • @InfoWorld
      @InfoWorld  6 หลายเดือนก่อน

      When you use pyproject.toml and create an editable install of your package, the .egg-info directory is side by side with the directory where the source for the package is. E.g., if you have /src/myapp, it'll be /src/myapp.egg-info
      -Serdar

  • @xzenor
    @xzenor ปีที่แล้ว +1

    That was useful. Thanks. Great explanation

  • @serufim
    @serufim 11 หลายเดือนก่อน +2

    God dam. i have learn python when an actual version was 3.5 and since python project have changed so much, that i think that python today and 7 years ago its quite different languages and i have to learn it again

  • @bryanrosiles899
    @bryanrosiles899 9 หลายเดือนก่อน +1

    You are a saint, thank you!

  • @pettymanny6487
    @pettymanny6487 6 หลายเดือนก่อน +2

    Useful, thanks

    • @InfoWorld
      @InfoWorld  6 หลายเดือนก่อน

      You're welcome.
      -Serdar

  • @johncompassion9054
    @johncompassion9054 11 หลายเดือนก่อน

    Thank you so much. Can you please explain what are .venv, .gitignore, input.md? And the general directory structure. Thank you again.

    • @ashrasmun1
      @ashrasmun1 11 หลายเดือนก่อน

      .venv is a directory created when you create a python virtual environment using virtualenv module. It basically ensures, that whatever you install, it's only available within that environment instead of whole system. You may want to read about it in detail more.
      .gitignore is a file in which you list which files you would like to ignore when commiting to your git repository. You may want to read more about "git" to understand context a bit better.

  • @xzenor
    @xzenor ปีที่แล้ว +1

    So you don't need a requirements.txt anymore but 'can' you add one anyway for people that prefer it? Or would that cause conflicts?

    • @InfoWorld
      @InfoWorld  ปีที่แล้ว +1

      You can use a requirements.txt side by side with a pyproject.toml file, but it would be your responsibility to keep the requirements in sync with each other in both files. My own personal feeling is to use one or the other, as a signal to the user about how to handle things.

  • @jamieo8307
    @jamieo8307 ปีที่แล้ว

    🙋 'PromoSM'