Skip to content

Updated resources.md with detailed local install instructions #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

t-redactyl
Copy link
Contributor

Hi everyone!

To complement the local install instructions and fulfill our sponsorship agreement with JetBrains, I've overhauled the resources.md page with detailed instructions on how to install everything locally. This is intended to give explanations for complete beginners. I went into this much detail as I've had similar conversations with people at some of the workshops, where they want to know not only how to do things, but why they need to do them.

I realised I didn't add the UV instructions, let me know if I should add them as well, but I wanted to keep it simple and not confuse beginners with too many frameworks.

@t-redactyl t-redactyl requested review from Cheukting and laisbsc May 20, 2025 11:43
Copy link
Contributor

@laisbsc laisbsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so very much for putting this together @t-redactyl <3 I've left a few comments but overall it is truly great!


To create a virtual environment, open a terminal window and navigate to the directory containing the repo with the Humble Data materials that you just cloned. Do this using the `cd` command we used in the last section when we cloned the repo - see if you can work out how to apply this to getting inside the folder containing the workshop materials!

Once you're inside this directory, type `python3 -m venv myvenv` at the terminal prompt. This is going to create a new folder inside the directory called "myvenv". This contains a bunch of code to make the virtual environment work. To use the virtual environment, we need to run a piece of this code, which will activate the virtual environment. At the terminal prompt, type:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we say that myenv can also have any other name they wanna use?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that's a great idea!


Activating the virtual environment allows us to go "inside" of it and install and use whatever packages we like, isolated from the rest of the system. You'll know it worked if the name of the virtual environment appears in parentheses somewhere in your terminal prompt (e.g., `(myvenv) PS C:\path\to\your\project>`).

To finish, we can install the packages we need to run the workshop materials. The packages we will need are:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we maybe add the command to install all libraries inside the requirements.txt here?
pip install -r requirements.txt on UNIX systems (using pip).

We have now instructions on how to do it using uv on the readme.md of the workshop as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll leave this up to you to decide @hevansDev :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, great idea to include the basic python venv method.

@hevansDev
Copy link
Collaborator

hevansDev commented Jun 13, 2025

Suggested a minor change to the opening to more clearerly stress what the two options for accessing the resources are and who they are for with a focus on jupyter server as more of a "default" option and local install as an alternative for students who want to learn to manage their own python environment.

Otherwise this new guide looks fantastic @t-redactyl!

Co-authored-by: Lais Carvalho <lais.bsc@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants