{"action":"opened","issue":{"url":"https://api.github.com/repos/pytest-dev/pytest/issues/1459","repository_url":"https://api.github.com/repos/pytest-dev/pytest","labels_url":"https://api.github.com/repos/pytest-dev/pytest/issues/1459/labels{/name}","comments_url":"https://api.github.com/repos/pytest-dev/pytest/issues/1459/comments","events_url":"https://api.github.com/repos/pytest-dev/pytest/issues/1459/events","html_url":"https://github.com/pytest-dev/pytest/issues/1459","id":141649046,"number":1459,"title":"Help request: debugging scope-related failure","user":{"login":"Zearin","id":630124,"avatar_url":"https://avatars.githubusercontent.com/u/630124?v=3","gravatar_id":"","url":"https://api.github.com/users/Zearin","html_url":"https://github.com/Zearin","followers_url":"https://api.github.com/users/Zearin/followers","following_url":"https://api.github.com/users/Zearin/following{/other_user}","gists_url":"https://api.github.com/users/Zearin/gists{/gist_id}","starred_url":"https://api.github.com/users/Zearin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Zearin/subscriptions","organizations_url":"https://api.github.com/users/Zearin/orgs","repos_url":"https://api.github.com/users/Zearin/repos","events_url":"https://api.github.com/users/Zearin/events{/privacy}","received_events_url":"https://api.github.com/users/Zearin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-17T17:19:40Z","updated_at":"2016-03-17T17:19:40Z","closed_at":null,"body":"## Description\r\n\r\n- I’m testing a different testing framework using pytest\r\n    - (FYI: I love pytest!  I actually discovered it in the process of working on this other project.  So I’m still a bit new to some of the magic pytest uses, but know that I plan on sticking with pytest for most projects in the future. ☻)\r\n- The project is currently **pre-alpha**; for now it is only being written for Python 3 (Python 2 support is planned once out of pre-alpha)\r\n- Pytest does some scope-related magic\r\n- The project *also* needs to properly manage scopes\r\n- Something scope-related is causing the test to fail, but I cannot determine why\r\n\r\nThe test needs to:\r\n\r\n- declare a function-level variable, `result`\r\n- run the fake tests (which contain nested functions, which are supposed to modify `result`)\r\n- run assertions on `result` (to verify that the fake tests executed properly)\r\n\r\n\r\n### Special Request\r\n\r\nThe project repository is currently private on GitHub.  I plan on making it public, but I want to get it to a minimally viable state first.  Therefore, if anyone on the pytest-dev team has a really solid knowledge of how Python scoping works—when doing weird things like testing a testing framework, each of which deviates from the scoping behavior of “normal” code—please add a comment, and I will add you as a collaborate to the project so you can run the test yourself.  \r\n\r\nThank you!   :D\r\n\r\n\r\n## `pip list`\r\n\r\n(Remember Python 3!  It’s really `pip3 list`, and the virtual env was created using `python3 -m venv`.)\r\n\r\n```\r\nappnope (0.1.0)\r\nastroid (1.4.4)\r\nblessings (1.6)\r\ncolorama (0.3.7)\r\ndecorator (4.0.9)\r\ndocopt (0.6.2)\r\neventemitter (0.2.0)\r\ngherkin-official (3.2.0)\r\ngnureadline (6.3.3)\r\nipython (4.1.2)\r\nipython-genutils (0.1.0)\r\nlazy-object-proxy (1.2.1)\r\npath.py (8.1.2)\r\npexpect (4.0.1)\r\npickleshare (0.6)\r\npip (8.1.1)\r\nptyprocess (0.5.1)\r\npy (1.4.31)\r\npyee (1.0.2)\r\npylint (1.5.4)\r\npytest (2.9.0)\r\npytest-asyncio (0.3.0)\r\npytest-catchlog (1.2.2)\r\npytest-colordots (0.1)\r\npytest-pylint (0.4.1)\r\nsetuptools (20.3)\r\nsimplegeneric (0.8.1)\r\nsix (1.10.0)\r\ntermcolor (1.1.0)\r\ntraitlets (4.2.1)\r\nUnidecode (0.4.19)\r\nwrapt (1.10.6)\r\n```\r\n\r\nIf you really know your scoping, let me know, and I’ll add to the private repo."}}