DOC: Removed line about %S parses all the way up to nanosecond even if no
State: closed

…decimal place present from docstring

- [ ] closes #49231
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).



Labels:
name: Docs
name: Datetime
description: Datetime data dtype

Comments:
Thanks for starting this

Could you also link to the issue in the issue description please?
Hi I am a bit confused as to how I can add the issue number in the issue description Could you please clarify as to what exactly that means
sure - where it says `closes #xxxx `, replace `xxxx` with the issue number of the issue which this pull request is closing, see https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue

regarding the CI failure, it should be enough to run the `black` formatter on the file you've modified, I think there's just some trailing whitespace
Hi,
With the exception of two tests all tests hava passed. However, I do not understand why the two tests have not passed. I am attaching screenshots of the error messages. 
This is the error message for the AVS Benchmarks test
![ASV Benchmarks](https://user-images.githubusercontent.com/111774640/198412264-7cd27d90-0482-4032-90ba-97b31bd0ba3a.jpg)
This is the error for the Data Manager test
![data manager error](https://user-images.githubusercontent.com/111774640/198412310-e77c619f-5282-496d-9a7f-465d57111508.jpg)
If you could please explain to me whats causing these errors I shall fix them ASAP
the errors look unrelated (general tip - don't attach screenshots as they're not searchable, just copy-and-paste the text)
> (general tip - don't attach screenshots as they're not searchable, just copy-and-paste the text) 

Thank you I shall keep that in mind.
> the errors look unrelated 

Ah ok. Well, is there any way we can remove the tests somehow or will that not be necessary?

Thanks a lot @MarcoGorelli ! This was my first contribution and it definitely was a lot of fun so this definitely won't be my last :) 
![A GIF History of Leonardo DiCaprio Raising Glasses](https://user-images.githubusercontent.com/111774640/198533337-bba1b746-41d4-4a9b-95cc-02f57368fe41.gif)

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
git checkout 1.5.x
git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
git cherry-pick -x -m1 cb42e052416d0d0f33ff8ba9bdbaf8bfa383c15b
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
git commit -am 'Backport PR #49349:  DOC: Removed line about %S parses all the way up to nanosecond even if no'
```

4. Push to a named branch:

```
git push YOURFORK 1.5.x:auto-backport-of-pr-49349-on-1.5.x
```

5. Create a PR against branch 1.5.x, I would have named this PR:

> "Backport PR #49349 on branch 1.5.x ( DOC: Removed line about %S parses all the way up to nanosecond even if no)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                
no need to backport, the original PR never made it in to 1.5.0