remove model.predict()

[zeke]

This PR removes the model.predict() method. If someone tries to call it they'll get an exception.

Normally it would make sense to deprecate stuff like this, but maybe since it's early days we can just break it.

This would be a great time to start using Semantic Versioning. We could call this 1.0.0, since it's a breaking change.

Resolves #69

[erbridge]

This looks fine. I'd suggest we can treat 0.x bumps as "major" until we hit 1.x, though, so don't need to bump up to "stable" just for this.

[bfirsh]

👍 Perhaps we wait until we have a JS client that matches the Python client then we could increment them to 1.0 at the same time and keep them more-or-less in line with each other.

[zeke]

🚢 https://github.com/replicate/replicate-python/releases/tag/0.5.0

Here's how I did it:

$ git commit -am "bump version to 0.5.0"
[main f71eec6] bump version to 0.5.0
 1 file changed, 1 insertion(+), 1 deletion(-)


$ git checkout main
Already on 'main'
Your branch is ahead of 'origin/main' by 1 commit.
  (use "git push" to publish your local commits)


$ git checkout main
Already on 'main'
Your branch is ahead of 'origin/main' by 1 commit.
  (use "git push" to publish your local commits)


$ git tag 0.5.0


$ git push --tags
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 8 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 368 bytes | 368.00 KiB/s, done.
Total 4 (delta 2), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
To https://github.com/replicate/replicate-python
 * [new tag]         0.5.0 -> 0.5.0