|
11 | 11 | "\n", |
12 | 12 | "## Lectures\n", |
13 | 13 | "\n", |
14 | | - "This course consists of four lectures:\n", |
| 14 | + "This course consists of five compulsory lectures:\n", |
15 | 15 | "\n", |
16 | 16 | "* [Lecture 1](./lecture1/lecture1.ipynb)\n", |
17 | 17 | "* [Lecture 2](./lecture2/lecture2.ipynb)\n", |
18 | 18 | "* [Lecture 3](./lecture3/lecture3.ipynb)\n", |
19 | 19 | "* [Lecture 4](./lecture4/lecture4.ipynb)\n", |
| 20 | + "* [Lecture 5](./lecture5/lecture5.ipynb)\n", |
| 21 | + "\n", |
| 22 | + "and one optional:\n", |
| 23 | + "\n", |
| 24 | + "* [Lecture 6](./lecture4/lecture6.ipynb)\n", |
20 | 25 | "\n", |
21 | 26 | "We strongly recommend completing them in this order.\n", |
22 | 27 | "\n", |
|
29 | 34 | "\n", |
30 | 35 | "It is important to follow the instructions for each exercise exactly and do not change the names of variables, functions, or classes so that tests can analyse your code. Besides, please do not change the content of any of the testing cells.\n", |
31 | 36 | "\n", |
32 | | - "Although **PyBryt** provides much more detailed feedback, it is possible it complains about your code even though **assert** statement confirms your code is correct. This is because PyBryt testing is based on comparing your solution to reference solutions. Since there is virtually an infinite number of alternative solutions, it is possible that your solution is not in our references. On the other hand, assert statements check the final result of your code and if they do not raise an error, your code is correct and you do not have to address **PyBryt**'s error messages (if any).\n", |
33 | | - "\n", |
34 | | - "## Support\n", |
35 | | - "\n", |
36 | | - "**We encourage questions!** If you require support, have questions, want to report a bug, or want to suggest an improvement, please raise an issue in the [course repository](https://github.com/ese-msc/introduction-to-python).\n", |
37 | | - "\n", |
38 | | - "> **Q:** I don't know where to ask my question. It might be related to something else, but I'm unsure. What should I do? \n", |
39 | | - "> **A:** Open an issue in this repository. This is a safe, respectful space to ask questions and open issues.\n", |
40 | | - "\n", |
41 | | - "> **Q:** I've never opened an issue. How do I do it? \n", |
42 | | - "> **A:** Click the `Issues` tab next to top of the page, then click the green `New Issue` button. Ask your question in the title and comment fields, then click `Submit new issue`. Congratulations, you submitted your question! We will try to get back to you shortly.\n", |
43 | | - "\n", |
44 | | - "> **Q:** How can I see if somebody else had the same or similar question? \n", |
45 | | - "> **A:** When you click the `Issues` tab next to top of the page, you can see all issues that are currently open and are being addressed. In addition to them, you can also check the issues that have been resolved in [closed issues](https://github.com/ese-msc/introduction-to-python/issues?q=is%3Aissue+is%3Aclosed).\n", |
46 | | - "\n", |
47 | | - "Are you a community member that enjoys sharing your knowledge and helping others solve problems? We encourage you to respond to these issues." |
| 37 | + "Although **PyBryt** provides much more detailed feedback, it is possible it complains about your code even though **assert** statement confirms your code is correct. This is because PyBryt testing is based on comparing your solution to reference solutions. Since there is virtually an infinite number of alternative solutions, it is possible that your solution is not in our references. On the other hand, assert statements check the final result of your code and if they do not raise an error, your code is correct and you do not have to address **PyBryt**'s error messages (if any)." |
48 | 38 | ] |
49 | 39 | } |
50 | 40 | ], |
|
0 commit comments