Please file an issue on github with reproducible code sample and also what you expect for PyScope. From a quick glance I do not see any issue with using the globals across scopes, see examples from @yagweb in his pull request and in the tests. You can define globals outside of scope. The NUnit tests are discoverable in VS, but if you set 64-bit architecture, then some tweaking is required: https://stackoverflow.com/questions/5571699/how-do-i-get-unit-tests-to-run-o... On Tue, Jun 27, 2017 at 8:28 AM, WARD Steve <Steve.Ward@oxinst.com> wrote:

Hi Denis,

I’ve had to stop development for now because PyScope global variables don’t seem to be working in similar fashion to IronPython. I want a global variable assigned at start-up with PyScope.Set(name,value), where value is most likely a .NET object, to be available later on in any module I might import.

I could try things out with the NUnit testing framework in the pythonnet solution but the tests are not listed in Visual Studio for some reason.

Steve

___________________________________________________________________________ This e-mail is confidential and is for the addressee only. Please refer to www.oxinst.com/email-statement for regulatory information.

_________________________________________________ Python.NET mailing list - PythonDotNet@python.org https://mail.python.org/mailman/listinfo/pythondotnet