minor fixing

[slowy07]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #409 🦕

[tseaver]

Thanks for the patch! Unfortunately, both these files are generated code, and would need fixing up in their source template, rather than in this repository.

The whitespace and lambda fixes should be trivial to do there: the cst.Element one, however, is apparently gnarly: @software-dov has a comment there referring the the "log chipper" formatting which happens.

@busunkim96, @parthea could we perhaps run black over the scripts/ directory via owlbot.py to make these fixes in place?

[slowy07]

Thanks for the patch! Unfortunately, both these files are generated code, and would need fixing up in their source template, rather than in this repository.

The whitespace and lambda fixes should be trivial to do there: the cst.Element one, however, is apparently gnarly: @software-dov has a comment there referring the the "log chipper" formatting which happens.

@busunkim96, @parthea could we perhaps run black over the scripts/ directory via owlbot.py to make these fixes in place?

okay,sorry for changes sir @tseaver

[parthea]

This was fixed in googleapis/gapic-generator-python#963 . We should see these changes in the next gapic generator update.

[slowy07]

This was fixed in googleapis/gapic-generator-python#963 . We should see these changes in the next gapic generator update.

okay thanks @parthea !, and sorry for the change make mess up