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

Legacy update to work with Py 2 and Py 3 #3

Merged
merged 1 commit into from
Feb 9, 2016

Conversation

Mr-TaylorHobbs
Copy link
Contributor

This build will not quite pass because of the apysigner and generic request signer not yet being on pypi. I am planning to wait until the office is a bit more healthy and jenkins is not lighting up like christmas to add them to pypi.

@Mr-TaylorHobbs
Copy link
Contributor Author

I also need to push up the correct requirements for this PR, but do not have access to push.

@mattjmorrison-imt
Copy link
Contributor

@Mr-TaylorHobbs it looks like the legacy branch needs protected also... let me know if/when you come across other repos that need that done.

@imtapps imtapps closed this Jan 22, 2016
@imtapps imtapps reopened this Jan 22, 2016
@Mr-TaylorHobbs
Copy link
Contributor Author

@mattjmorrison-imt does the repo need to be set up to build PRs for the legacy branch too?

@Mr-TaylorHobbs
Copy link
Contributor Author

image

Not sure if my comment triggered it or if you set it up at the same time...

@mattjmorrison-imt
Copy link
Contributor

@Mr-TaylorHobbs I did nothing...

@Mr-TaylorHobbs
Copy link
Contributor Author

Well huh. Cool either way I guess

mattjmorrison-imt pushed a commit that referenced this pull request Feb 9, 2016
Legacy update to work with Py 2 and Py 3
@mattjmorrison-imt mattjmorrison-imt merged commit 5e75ec4 into legacy Feb 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants