BUG: Eval scopes ignoring empty dictionaries (#47084)
closes  [#47084](https://github.com/pandas-dev/pandas/issues/47084)

- [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).
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Hello @Alex-Blade! 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:







There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2022-06-04 10:38:38 UTC looks ok, need to do precommit here (line length). can you add a whatsnew note for this. @github-actions pre-commit @jreback, to be honest, I don't really get how should I name the entry in the `_whatsnew_150.bug_fixes` section. Some of them are named according to classnames (`Categorical` - Bug in `Categorical.view`). Others imply an action during which users may encounter the bug (`Indexing` - Bug in `loc.__getitem__`). Is there a list of predefined sections perhaps? UPD. Rebased and made an entry in Other section, by analogy with similar bug-fixes from previous versions  @jreback, mind looking at it again? > @jreback, mind looking at it again?

@Alex-Blade ci is failing. reviewers (other than Jeff) are more likely to review PRs with green ci.

code checks and some pytables tests are failing.

@jreback since the issue suggested this as being an security concern, would we consider this for 1.4.x (once ci is green)? see here: https://github.com/pandas-dev/pandas/runs/6660273116?check_suite_focus=true

looks like the precommit is failing @github-actions pre-commit Seems like Numpy Dev died by an accident on setup-miniconda stage These tests are painful... Two times they died because of numpy, and now a timeout...
 @simonjayhawkins, it has passed the tests a few times in a row, I think it can be considered as ready thanks @Alex-Blade very nice! @meeseeksdev backport 1.4.x Could not push to auto-backport-of-pr-47085-on-1.4.x due to error, aborting.