Skip to content
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 resources for python 3.8 #45629

Closed

Conversation

bayandin
Copy link
Member

@bayandin bayandin commented Oct 21, 2019

  • Have you followed the guidelines for contributing?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

As it appears, python 3.8 migration quite a big thing, so I cherry-picked resource updates from #45337 to make sure that failures are not related to resources

@bayandin bayandin mentioned this pull request Oct 21, 2019
10 tasks
@bayandin bayandin changed the title Update resources for python3.8 Update resources for python 3.8 Oct 21, 2019
@bayandin
Copy link
Member Author

bayandin commented Oct 21, 2019

@fxcoudert fxcoudert closed this in c7340c6 Oct 22, 2019
@fxcoudert
Copy link
Member

Thanks @bayandin, I've merged everything except ansible-lint. For salt, we'll reassess with Python 3.8.0

@bayandin bayandin deleted the update-resources-for-python3.8 branch October 22, 2019 09:39
@bayandin
Copy link
Member Author

Thanks!

@lock lock bot added the outdated PR was locked due to age label Jan 5, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Jan 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated PR was locked due to age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants