Adding extended setup instructions#470
Conversation
maxim-belkin
left a comment
maxim-belkin
left a comment
There was a problem hiding this comment.
Thank you, Toni! It looks fantastic. I made some stylistic comments -- please address them when you get a chance.
Thank you for your contribution!
| > version 3.x (e.g., 3.6 is fine). Also, please set up your Python environment at | ||
| > least a day in advance of the workshop. If you encounter problems with the | ||
| > installation procedure, ask your workshop organizers via e-mail for assistance so | ||
| > you are ready to go as soon as the workshop begins. |
There was a problem hiding this comment.
I agree it is useful to remind participants to prepare a bit in advance. But currently it's a bit hidden. Do you have any suggestions how we could make it more visible?
There was a problem hiding this comment.
I am not sure where a good place for this would be. I tend to highlight this in an email I send out to participants before a workshop.
There was a problem hiding this comment.
We send similar reminders/requests to workshop participants but I'm on the fence whether this should be part of the lesson -- when participants install software seems to be more appropriate for a workshop page where all event-related questions are handled.
There was a problem hiding this comment.
Happy for this to be removed then. Though stating that python 3.x is required would be good I think.
There was a problem hiding this comment.
Yes, let's do that. And you can submit a PR to https://github.com/carpentries/workshop-template with this reminder, if it doesn't have one already.
There was a problem hiding this comment.
Ok will try and remember to do that.
| > a bit difficult, so we recommend an all-in-one installer. | ||
| > ## Installing Python using Anaconda | ||
| > [Python][python] is a popular language for scientific computing, and great for | ||
| > general-purpose programming as well. Installing all of its scientific packages |
There was a problem hiding this comment.
Do you think we should limit the range of "scientific packages" we talk about here to the ones we use in the lesson?
There was a problem hiding this comment.
I don't think so. This is just very confusing if you don't really know anything about python. I frequently have this with Ruby which I use very rarely and get a bit overwhelmed with random package names.
There was a problem hiding this comment.
I meant something like Installing all of the scientific packages we use in the lesson individually...
maxim-belkin
added
the
status:waiting for response
Co-authored-by: Maxim Belkin <maxim.belkin@gmail.com>
Co-authored-by: Maxim Belkin <maxim.belkin@gmail.com>
Co-authored-by: Maxim Belkin <maxim.belkin@gmail.com>
Co-authored-by: Maxim Belkin <maxim.belkin@gmail.com>
Co-authored-by: Maxim Belkin <maxim.belkin@gmail.com>
Co-authored-by: Maxim Belkin <maxim.belkin@gmail.com>
Co-authored-by: Maxim Belkin <maxim.belkin@gmail.com>
Co-authored-by: Maxim Belkin <maxim.belkin@gmail.com>
|
Happy with all your suggestions and have committed them. See my other two comments. I don't have a quick solution for them, but happy to have another think about it when I run the next workshop. |
|
Ok I think I updated the above two comments as well now. |
Um... commit 300d0b5 deleted two empty lines |
maxim-belkin
added
type:enhancement
|
Ok how about now. Don't know what happened there. |
maxim-belkin
left a comment
maxim-belkin
left a comment
There was a problem hiding this comment.
Looks great! Thank you very much, Toni!
Adding extended setup instructions
2 participants
@maxim-belkin, I have made an attempt at improving the instructions for setup I had raised as #457. Some of it is directly copied from the Software carpentry setup instructions including the setup videos. Other bits I added myself.
Let me know if you want me to change anything further.
It may also be nice to change the html template for Python for DC lessons to look a bit more like the SC ones such as this one:
https://edcarp.github.io/2020-01-21-edinburgh-swc/
But I think this will require the change of the actual workshop-template.