-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
hhsecond
committed
Jul 18, 2019
1 parent
9ebcec0
commit 44e305e
Showing
11 changed files
with
35 additions
and
35 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,7 +15,7 @@ Types of Contributions | |
Report Bugs | ||
~~~~~~~~~~~ | ||
|
||
Report bugs at https://github.com/hhsecond/mlutil/issues. | ||
Report bugs at https://github.com/hhsecond/ml2rt/issues. | ||
|
||
If you are reporting a bug, please include: | ||
|
||
|
@@ -38,14 +38,14 @@ and "help wanted" is open to whoever wants to implement it. | |
Write Documentation | ||
~~~~~~~~~~~~~~~~~~~ | ||
|
||
MLutil could always use more documentation, whether as part of the | ||
official MLutil docs, in docstrings, or even on the web in blog posts, | ||
ml2rt could always use more documentation, whether as part of the | ||
official ml2rt docs, in docstrings, or even on the web in blog posts, | ||
articles, and such. | ||
|
||
Submit Feedback | ||
~~~~~~~~~~~~~~~ | ||
|
||
The best way to send feedback is to file an issue at https://github.com/hhsecond/mlutil/issues. | ||
The best way to send feedback is to file an issue at https://github.com/hhsecond/ml2rt/issues. | ||
|
||
If you are proposing a feature: | ||
|
||
|
@@ -57,17 +57,17 @@ If you are proposing a feature: | |
Get Started! | ||
------------ | ||
|
||
Ready to contribute? Here's how to set up `mlutil` for local development. | ||
Ready to contribute? Here's how to set up `ml2rt` for local development. | ||
|
||
1. Fork the `mlutil` repo on GitHub. | ||
1. Fork the `ml2rt` repo on GitHub. | ||
2. Clone your fork locally:: | ||
|
||
$ git clone [email protected]:your_name_here/mlutil.git | ||
$ git clone [email protected]:your_name_here/ml2rt.git | ||
|
||
3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:: | ||
|
||
$ mkvirtualenv mlutil | ||
$ cd mlutil/ | ||
$ mkvirtualenv ml2rt | ||
$ cd ml2rt/ | ||
$ python setup.py develop | ||
|
||
4. Create a branch for local development:: | ||
|
@@ -79,7 +79,7 @@ Ready to contribute? Here's how to set up `mlutil` for local development. | |
5. When you're done making changes, check that your changes pass flake8 and the | ||
tests, including testing other Python versions with tox:: | ||
|
||
$ flake8 mlutil tests | ||
$ flake8 ml2rt tests | ||
$ python setup.py test or py.test | ||
$ tox | ||
|
||
|
@@ -103,15 +103,15 @@ Before you submit a pull request, check that it meets these guidelines: | |
your new functionality into a function with a docstring, and add the | ||
feature to the list in README.rst. | ||
3. The pull request should work for Python 2.7, 3.4, 3.5 and 3.6, and for PyPy. Check | ||
https://travis-ci.org/hhsecond/mlutil/pull_requests | ||
https://travis-ci.org/hhsecond/ml2rt/pull_requests | ||
and make sure that the tests pass for all supported Python versions. | ||
|
||
Tips | ||
---- | ||
|
||
To run a subset of tests:: | ||
|
||
$ py.test tests.test_mlutil | ||
$ py.test tests.test_ml2rt | ||
|
||
|
||
Deploying | ||
|
This file contains 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
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains 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
This file contains 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
This file contains 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
This file contains 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