Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: shankarpandala/lazypredict
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: dev
Choose a base ref
...
head repository: nityansuman/lazypredict-nightly
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Can’t automatically merge. Don’t worry, you can still create the pull request.
  • 15 commits
  • 37 files changed
  • 1 contributor

Commits on Mar 2, 2024

  1. Update README.md

    nityansuman authored Mar 2, 2024
    Copy the full SHA
    004eccf View commit details
  2. Copy the full SHA
    7343eab View commit details
  3. Copy the full SHA
    49080fd View commit details
  4. Cleanup

    nityansuman committed Mar 2, 2024
    Copy the full SHA
    75baf72 View commit details
  5. Update README.md

    nityansuman authored Mar 2, 2024
    Copy the full SHA
    24e6e5b View commit details
  6. Minor cleanup

    nityansuman committed Mar 2, 2024
    Copy the full SHA
    29295a5 View commit details
  7. Cleanup

    nityansuman committed Mar 2, 2024
    Copy the full SHA
    b76c6c4 View commit details
  8. Copy the full SHA
    9b66b21 View commit details

Commits on Mar 7, 2024

  1. Updated structure

    nityansuman committed Mar 7, 2024
    Copy the full SHA
    7eb2035 View commit details

Commits on Mar 16, 2024

  1. Update README.md

    nityansuman authored Mar 16, 2024
    Copy the full SHA
    e69072e View commit details

Commits on Mar 25, 2024

  1. Update README.md

    nityansuman authored Mar 25, 2024
    Copy the full SHA
    4c2645d View commit details
  2. Fixed import error

    nityansuman committed Mar 25, 2024
    Copy the full SHA
    4912aee View commit details
  3. Copy the full SHA
    6bb089a View commit details
  4. Update README.md

    nityansuman authored Mar 25, 2024
    Copy the full SHA
    d52d220 View commit details
  5. Update README.md

    nityansuman authored Mar 25, 2024
    Copy the full SHA
    27d495c View commit details
26 changes: 0 additions & 26 deletions .circleci/config.yml

This file was deleted.

21 changes: 0 additions & 21 deletions .editorconfig

This file was deleted.

13 changes: 0 additions & 13 deletions .github/FUNDING.yml

This file was deleted.

43 changes: 0 additions & 43 deletions .github/workflows/build.yml

This file was deleted.

54 changes: 0 additions & 54 deletions .github/workflows/codeql-analysis.yml

This file was deleted.

35 changes: 0 additions & 35 deletions .github/workflows/docs.yml

This file was deleted.

29 changes: 0 additions & 29 deletions .github/workflows/publish.yml

This file was deleted.

34 changes: 0 additions & 34 deletions .travis.yml

This file was deleted.

13 changes: 6 additions & 7 deletions AUTHORS.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,10 @@
---
title: Credits
Credits
---

# Development Lead
# Maintainer
- Kumar Nityan Suman \<<nityan.suman@gmail.com>\>

- Shankar Rao Pandala \<<shankar.pandala@live.com>\>

# Contributors

- Breno Batista da Silva \<<brenophp@gmail.com>\>
# Inspired Work From
- Shankar Rao Pandala \<<shankar.pandala@live.com>\>
- Breno Batista da Silva \<<brenophp@gmail.com>\>
18 changes: 9 additions & 9 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -11,7 +11,7 @@ You can contribute in many ways:

## Report Bugs

Report bugs at <https://github.com/shankarpandala/lazypredict/issues>.
Report bugs at <https://github.com/nityansuman/lazypredict-nightly/issues>.

If you are reporting a bug, please include:

@@ -40,7 +40,7 @@ posts, articles, and such.
## Submit Feedback

The best way to send feedback is to file an issue at
<https://github.com/shankarpandala/lazypredict/issues>.
<https://github.com/nityansuman/lazypredict-nightly/issues>.

If you are proposing a feature:

@@ -52,24 +52,24 @@ If you are proposing a feature:

# Get Started!

Ready to contribute? Here\'s how to set up [lazypredict]{.title-ref} for
Ready to contribute? Here\'s how to set up [lazypredict-nightly]{.title-ref} for
local development.

1. Fork the [lazypredict]{.title-ref} repo on GitHub.
1. Fork the [lazypredict-nightly]{.title-ref} repo on GitHub.

2. Clone your fork locally:

``` shell
$ git clone git@github.com:your_name_here/lazypredict.git
$ git clone git@github.com:your_name_here/lazypredict-nightly.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:

``` shell
$ mkvirtualenv lazypredict
$ cd lazypredict/
$ mkvirtualenv lazypredict-nightly
$ cd lazypredict-nightly/
$ python setup.py develop
$ pip install -r requirements_dev.txt
```
@@ -87,7 +87,7 @@ local development.
tox:

``` shell
$ flake8 lazypredict tests
$ flake8 lazypredict-nightly tests
$ python setup.py test or pytest
$ tox
```
@@ -114,7 +114,7 @@ Before you submit a pull request, check that it meets these guidelines:
the feature to the list in README.rst.
3. The pull request should work for Python 2.7, 3.5, 3.6, 3.7 and 3.8,
and for PyPy. Check
<https://travis-ci.org/shankarpandala/lazypredict/pull_requests> and
<https://travis-ci.org/nityansuman/lazypredict-nightly/pull_requests> and
make sure that the tests pass for all supported Python versions.

# Tips
15 changes: 14 additions & 1 deletion HISTORY.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,20 @@
---
title: History
History
---

# 0.3.2 (2024-03-25)

- Major import bug fix
- Cleanup

# 0.3.1 (2024-03-03)

- Minor cleanups

# 0.3.0 (2024-03-03)

- Fixed OneHotEncoder Bug

# 0.2.11 (2022-02-06)

- Updated the default version to 3.9
21 changes: 4 additions & 17 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -1,22 +1,9 @@
MIT License

Copyright (c) 2020, Shankar Rao Pandala
Copyright 2024 Lazy Predict Nightly Developers and Contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Loading