TST: Ensure tm.network has pytest.mark.network
State: closed

- [x] closes #45085 (Replace xxxx with the Github issue number)
- [x] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).

* Ensure `tm.network` is paired with `@pytest.mark.network`
* Refactored test (by downloading data directly) that is not testing networking specifically


Labels:
name: Testing
description: pandas testing functions or related to the test suite
name: IO Network
description: Local or Cloud (AWS, GCS, etc.) IO Issues

Comments:
hmm there is an included `teams.cvs` is that intentional?
> hmm there is an included `teams.cvs` is that intentional?

Yes this is expected. It was the test I referenced as "Refactored test (by downloading data directly) that is not testing networking specifically"
@meeseeksdev backport 1.4.x
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.4.x
git pull
```

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

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

```
git commit -am 'Backport PR #45732: TST: Ensure tm.network has pytest.mark.network'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-45732-on-1.4.x
```

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

> "Backport PR #45732 on branch 1.4.x (TST: Ensure tm.network has pytest.mark.network)"

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).
                
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.4.x
git pull
```

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

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

```
git commit -am 'Backport PR #45732: TST: Ensure tm.network has pytest.mark.network'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-45732-on-1.4.x
```

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

> "Backport PR #45732 on branch 1.4.x (TST: Ensure tm.network has pytest.mark.network)"

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).