ERR: better error message with invalid argument in sort_values
- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry
added a if branch to check the ascending type, as the existing one accepts value with string as well instead of boolean.

k=df.sort_values(by=['col1'],ascending="False") does not give exception with str.
added piece of code to raise exception if the type is not boolean



Hello @deej197! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:

* In the file [`pandas/core/series.py`](https://github.com/pandas-dev/pandas/blob/d064edc441dcc16033d9c002bdfefb5cc04ea3aa/pandas/core/series.py):

> [Line 3444:1](https://github.com/pandas-dev/pandas/blob/d064edc441dcc16033d9c002bdfefb5cc04ea3aa/pandas/core/series.py#L3444): [W293](https://duckduckgo.com/?q=pep8%20W293) blank line contains whitespace
> [Line 3445:9](https://github.com/pandas-dev/pandas/blob/d064edc441dcc16033d9c002bdfefb5cc04ea3aa/pandas/core/series.py#L3445): [E303](https://duckduckgo.com/?q=pep8%20E303) too many blank lines (2)
> [Line 3445:27](https://github.com/pandas-dev/pandas/blob/d064edc441dcc16033d9c002bdfefb5cc04ea3aa/pandas/core/series.py#L3445): [E225](https://duckduckgo.com/?q=pep8%20E225) missing whitespace around operator



##### Comment last updated at 2021-07-03 19:22:47 UTC Thanks for the contribution @deej197, but unfortunately you won't be able to contribute with a proper development environment. If you could run this test locally you could see that:
- It's adding new bugs, and doesn't affect the current one
- The problem is not the one you mention in the title, the error message is fine, the problem is that it only raises on `Series`, and not in `DataFrame`.

And it's also better to start by opening an issue, finding a reproducible example, and when there is agreement with the solution, then open the PR (which would require tests and a release note, besides the code changes). I opened an issue myself, so you can see how would be better to start: #42434. Feel free to work on the issue, but as I said, you need a working development environment. Otherwise you won't be able to test what you're doing, and you'll be submitting obviously wrong PRs like this, that don't add value, and waste reviewers time.

If you follow the contribution guide, you shouldn't have problems setting up the develoment environment, if something is not clear enough, feel free to open an issue to ask for clarification in the docs.