8000 Remove unnecessary typing dependency. by ezyang · Pull Request #16776 · pytorch/pytorch · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
8000

Remove unnecessary typing dependency. #16776

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

Merged
merged 1 commit into from
Feb 7, 2019

Conversation

ezyang
Copy link
Contributor
@ezyang ezyang commented Feb 5, 2019

Signed-off-by: Edward Z. Yang ezyang@fb.com

Signed-off-by: Edward Z. Yang <ezyang@fb.com>
@ezyang
Copy link
Contributor Author
ezyang commented Feb 5, 2019

Companion PR for master: #16777

@ezyang ezyang requested a review from zou3519 February 5, 2019 20:55
Copy link
Contributor
@zou3519 zou3519 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. @soumith should we rebuild the binaries with this?

@soumith soumith merged commit 8322165 into pytorch:v1.0.1 Feb 7, 2019
@soumith soumith added this to the 1.0.1 milestone Feb 7, 2019
@kevin-hanselman
Copy link

Maybe I'm missing something, but it looks like the setup.py still requires typing?

https://github.com/pytorch/pytorch/blob/v1.0.1/setup.py#L331

@soumith
Copy link
Member
soumith commented Feb 7, 2019

@kevlar1818 that's required for build-time (i.e. when compiling), but not runtime.

@fmassa
Copy link
Member
fmassa commented Feb 7, 2019

is this PR related to the failing tests in pytorch/vision#736 in any way?

@ezyang
Copy link
Contributor Author
ezyang commented Feb 7, 2019

@fmassa Yes, it looks exactly like this. If you manually install typing in your environments, that should unbreak vision CI.

@soumith
Copy link
Member
soumith commented Feb 8, 2019

new binaries uploaded, this should be fixed now.

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.

5 participants
0