New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default module name when __name__ not set #374

Merged
merged 3 commits into from Oct 17, 2018

Conversation

Projects
None yet
3 participants
@alubbock
Member

alubbock commented Sep 11, 2018

The module/function name is captured by PySB when Components
are defined, but in some interpreters the __name__ attribute
is not set for interactive sessions. To avoid an error, this
introduces a default value of __unnamed__.

Set module name when __name__ is not set
The module/function name is captured by PySB when Components
are defined, but in some interpreters the __name__ attribute
is not set for interactive sessions. To avoid an error, this
introduces a default value of __unnamed__.
@coveralls

This comment has been minimized.

coveralls commented Sep 11, 2018

Coverage Status

Coverage remained the same at 79.179% when pulling eadd753 on alubbock:fix_modname_core into 99d335e on pysb:master.

Show resolved Hide resolved pysb/core.py Outdated

@alubbock alubbock merged commit 10f8713 into pysb:master Oct 17, 2018

2 of 3 checks passed

continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage remained the same at 79.179%
Details

@alubbock alubbock deleted the alubbock:fix_modname_core branch Oct 17, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment