mirror of
https://github.com/Xevion/exercism.git
synced 2025-12-09 14:07:10 -06:00
77 lines
3.0 KiB
Markdown
77 lines
3.0 KiB
Markdown
# Meetup
|
|
|
|
Calculate the date of meetups.
|
|
|
|
Typically meetups happen on the same day of the week. In this exercise, you
|
|
will take a description of a meetup date, and return the actual meetup date.
|
|
|
|
Examples of general descriptions are:
|
|
|
|
- The first Monday of January 2017
|
|
- The third Tuesday of January 2017
|
|
- The wednesteenth of January 2017
|
|
- The last Thursday of January 2017
|
|
|
|
The descriptors you are expected to parse are:
|
|
first, second, third, fourth, fifth, last, monteenth, tuesteenth, wednesteenth,
|
|
thursteenth, friteenth, saturteenth, sunteenth
|
|
|
|
Note that "monteenth", "tuesteenth", etc are all made up words. There was a
|
|
meetup whose members realized that there are exactly 7 numbered days in a month
|
|
that end in '-teenth'. Therefore, one is guaranteed that each day of the week
|
|
(Monday, Tuesday, ...) will have exactly one date that is named with '-teenth'
|
|
in every month.
|
|
|
|
Given examples of a meetup dates, each containing a month, day, year, and
|
|
descriptor calculate the date of the actual meetup. For example, if given
|
|
"The first Monday of January 2017", the correct meetup date is 2017/1/2.
|
|
|
|
## Exception messages
|
|
|
|
Sometimes it is necessary to raise an exception. When you do this, you should include a meaningful error message to
|
|
indicate what the source of the error is. This makes your code more readable and helps significantly with debugging. Not
|
|
every exercise will require you to raise an exception, but for those that do, the tests will only pass if you include
|
|
a message.
|
|
|
|
To raise a message with an exception, just write it as an argument to the exception type. For example, instead of
|
|
`raise Exception`, you should write:
|
|
|
|
```python
|
|
raise Exception("Meaningful message indicating the source of the error")
|
|
```
|
|
|
|
## Running the tests
|
|
|
|
To run the tests, run the appropriate command below ([why they are different](https://github.com/pytest-dev/pytest/issues/1629#issue-161422224)):
|
|
|
|
- Python 2.7: `py.test meetup_test.py`
|
|
- Python 3.4+: `pytest meetup_test.py`
|
|
|
|
Alternatively, you can tell Python to run the pytest module (allowing the same command to be used regardless of Python version):
|
|
`python -m pytest meetup_test.py`
|
|
|
|
### Common `pytest` options
|
|
|
|
- `-v` : enable verbose output
|
|
- `-x` : stop running tests on first failure
|
|
- `--ff` : run failures from previous test before running other test cases
|
|
|
|
For other options, see `python -m pytest -h`
|
|
|
|
## Submitting Exercises
|
|
|
|
Note that, when trying to submit an exercise, make sure the solution is in the `$EXERCISM_WORKSPACE/python/meetup` directory.
|
|
|
|
You can find your Exercism workspace by running `exercism debug` and looking for the line that starts with `Workspace`.
|
|
|
|
For more detailed information about running tests, code style and linting,
|
|
please see [Running the Tests](http://exercism.io/tracks/python/tests).
|
|
|
|
## Source
|
|
|
|
Jeremy Hinegardner mentioned a Boulder meetup that happens on the Wednesteenth of every month [https://twitter.com/copiousfreetime](https://twitter.com/copiousfreetime)
|
|
|
|
## Submitting Incomplete Solutions
|
|
|
|
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|