-
Notifications
You must be signed in to change notification settings - Fork 9
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
Update to work with pvsxlibs 1.3.0 #146
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #146 +/- ##
==========================================
- Coverage 87.73% 87.43% -0.30%
==========================================
Files 14 14
Lines 1019 1019
==========================================
- Hits 894 891 -3
- Misses 125 128 +3 ☔ View full report in Codecov by Sentry. |
2b26f4a
to
dccdeef
Compare
This version changed the name of its inbuilt .dbd files, which we must match in order to load it Also updated various other dependencies in order to make the pipenv environment stable
dccdeef
to
dd63ac8
Compare
@mdavidsaver is this the correct fix? |
This was not intentional (epics-base/pvxs#65). fyi. renaming/removal of a .dbd file is to my mind an incompatible API change, which would trigger a major version increment. |
Fixed in pvxslibs==1.3.1. I have "yanked" 1.3.0 on pypi.org. It would help in detecting issues like this if pythonSoftIOC could add a CI job testing the current 'master' branches of epicscorelibs, pvxs, and p4p. |
PR is no longer necessary. |
This version changed the name of its inbuilt .dbd files, which we must match in order to load it
Also updated various other dependencies in order to make the pipenv environment stable
Closes #145