[Python] Use explicit imports (again) - split up to avoid pygments issue in #757 #758
+35
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Running tests... |
|
Tests pass on OS X. |
gribozavr
added a commit
that referenced
this pull request
Dec 24, 2015
[Python] Use explicit imports (again) - split up to avoid pygments issue in #757
aciidgh
added a commit
to aciidgh/swift
that referenced
this pull request
Dec 21, 2016
- <rdar://problem/27791475> SwiftPM can now be built in release mode because all the outstanding issues preventing that has been resolved. The major issues were: * Building (and running) unit tests with @testable import in * release. (swiftpm PR swiftlang#758) * Linker errors when building unit tests with wmo on linux. (SR-3034)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to @eeckstein for noticing the pygments issue.