-
Notifications
You must be signed in to change notification settings - Fork 249
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
assert_can_execute breaking api change with addition of env parameter #762
Comments
Thanks for the report. I'll see if it's possible to default to a specific environment as a reasonable default, but even then the system might not work. |
Thanks, yea I know it changed with a minor version so it's understandable that you're not responsible for dealing with it but it would be nice to have that default if possible |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the addition of the env parameter, any plugin that called
assert_can_execute
prior to this will be broken. I'm attempting to use the pybuilder-docker plugin and am facing this issue. Can we give env a default of Noneenv=None
so that it remains backwards compatible for plugins that were potentially already using it?I created a pr for them to fix the issue, but I don't know if the plugin is being maintained or not.
for reference: AlienVault-Engineering/pybuilder-docker#7
The text was updated successfully, but these errors were encountered: