Pixi

[hmgaudecker]

• Update project itself
• Move python_installation_execution to conda subdirectory or so
  • environment.yml
  • Installation instructions
  • Executing notebooks in browser
  • Executing notebooks in VS Code
  • Executing .py files in terminal
  • Executing .py files in VS Code
  • Running code via pytask
  • Environment files and environments.
• Add pixi background x 2 (Tim: I've added the folder python_installation_executation/package_management. Must be revised however)
• Add pixi intro (how to use)
• Setting up a new project
• Directory structure in the templates (Very outdated)
• Handling paths in projects (conda activate is only seen very briefly)
• Update plotly installation lecture (removed the separate Windows instructions in 1769916)
• Add XCode to list of programs to install (when using MacOS) (came up in session 1 of epp leuven)

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[hmgaudecker]

* [ ]  Add XCode to list of programs to install (when using MacOS) (came up in session 1 of epp leuven)

@timmens, do you remember the details of this one? And it would go to the epp_(term|block)_course - repos, right? Or here?

@apitarch29 has just gotten started to update the materials for the winter term, so we might have more questions. Though I'll try to keep them to a minimum.

[timmens]

Sort of. If I remember correctly, when using a Mac for programming at some point you usually get prompted to install the Xcode Comand Line Tools (via xcode-select --install). This installs Apple’s clang/clang++, ld, make, git, headers + macOS SDK paths; which, I am guessing, makes installation of everything else through the tools we recommend much easier.

I think this prompting for installation happens so naturally (Apple style) that basically everyone installs this automatically; however, in Leuven someone did not, and that seemed to cause problems.

I could also imagine that we add a note to (1) the git installation page, and (2) the Python installation page you linked to ask MacOS users to install these tools beforehand / verify that they are installed (verify using xcode-select -p ).

[danielemauriello]

So, based on the information reported by Tim, Xcode is something we want students to install before starting any other installation procedure. Therefore, I would move the note about checking its installation at the beginning of each installation page (Git and Python) rather than at the end.

Also, based on these docs, the installation of Xcode doesn't seem so black and white. Again, based on the message from Tim, it seems that only not having Xcode at all is problematic. I think we can mention in our page that the manual installation of Xcode is needed only if the output of xcode-select -p is xcode-select: error: unable to get active developer directory....