How to Install Python 3.12 on mac OS (2024) + VS Code and Poetry with Homebrew

Поделиться
HTML-код
  • Опубликовано: 22 авг 2024

Комментарии • 4

  • @TanmaySahooP19MA001
    @TanmaySahooP19MA001 5 дней назад

    I followed your installation procedure. But two problems arise. I could not create a profile with data science, and it failed to detect the kernel. Can you help me with that?

    • @VincentCodesFinance
      @VincentCodesFinance  3 дня назад

      I can't say much without more information or the error messages you are getting. I never had any issue creating a profile. Maybe you could try to create an empty profile and manually add the extensions? As for the kernel, by default VS Code will look at some common locations for kernels, one of them being the .venv directory in your project (what VS Code calls "Folder"). You can always search manually for the kernel you want by clicking on "Kernel" in the interactive window, or by clicking on "Python" in the bottom right of the VS Code window when you have a .py file open.

  • @jobbjabb4815
    @jobbjabb4815 23 часа назад

    I have install python with this way (brew install python). Can I install packages with out creating .venv ? because I don't want to put all of my python files in that directory mostly in my one drive. I have tried to install by using "pip3 install" in the Terminal but it's not work.

    • @VincentCodesFinance
      @VincentCodesFinance  19 часов назад

      Brew now follows PEP 668 (see at the bottom of docs.brew.sh/Homebrew-and-Python), which means that you cannot install packages « globally », unless they are available in brew. There are good reasons for that (ie if your global environment becomes conflicted, it is a pain to fix), but that means that you need to create an environment in order to use pip. Ideally you want one environment by project, but I also keep one « playground » environment that I use for random scripts not part of a project. My preferred environment manager is poetry, but you can do the same with pyenv, just create an environment and activate it whenever you need it. You can configure it to be loaded by default in the terminal (in your .zshrc file) or in VS Code.