2016-10-27 01:27:56 +00:00
|
|
|
<!--- Provide a general summary of your changes in the Title -->
|
2016-10-27 01:20:08 +00:00
|
|
|
|
|
|
|
|
## Description
|
2016-10-27 01:27:56 +00:00
|
|
|
<!--- Describe your changes -->
|
2016-10-27 01:20:08 +00:00
|
|
|
|
|
|
|
|
## Motivation and Context
|
|
|
|
|
<!--- Why is this change required? What problem does it solve? -->
|
2016-10-27 01:27:56 +00:00
|
|
|
<!--- If fixing an open issue, please link to the issue here. -->
|
2016-10-27 01:20:08 +00:00
|
|
|
|
|
|
|
|
## How Has This Been Tested?
|
2016-10-27 01:27:56 +00:00
|
|
|
<!--- Please describe in detail your tests. Did you add new tests? -->
|
|
|
|
|
<!--- Include details of your testing environment, and the tests you ran too -->
|
|
|
|
|
<!--- How were other areas of the code affected? -->
|
2016-10-27 01:20:08 +00:00
|
|
|
|
|
|
|
|
## Types of changes
|
2016-10-27 01:27:56 +00:00
|
|
|
<!--- What types of changes does your code introduce? Put an `x` in all applicable boxes.: -->
|
|
|
|
|
- [ ] Bug fix (non-breaking change fixing an issue)
|
|
|
|
|
- [ ] New feature (non-breaking change adding functionality to spaCy)
|
|
|
|
|
- [ ] Breaking change (fix or feature causing change to spaCy's existing functionality)
|
|
|
|
|
- [ ] Documentation (Addition to documentation of spaCy)
|
2016-10-27 01:20:08 +00:00
|
|
|
|
|
|
|
|
## Checklist:
|
2016-10-27 01:27:56 +00:00
|
|
|
<!--- Go over all the following points, and put an `x` in all applicable boxes.: -->
|
|
|
|
|
- [ ] My code follows spaCy's code style.
|
|
|
|
|
- [ ] My change requires a change to spaCy's documentation.
|
2016-10-27 01:20:08 +00:00
|
|
|
- [ ] I have updated the documentation accordingly.
|
|
|
|
|
- [ ] I have added tests to cover my changes.
|
2017-01-03 14:41:16 +00:00
|
|
|
- [ ] All new and existing tests passed.
|
