Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tensorflow-ocaml.0.0.1 - via opam-publish #6152

Merged
merged 1 commit into from
Mar 31, 2016
Merged

tensorflow-ocaml.0.0.1 - via opam-publish #6152

merged 1 commit into from
Mar 31, 2016

Conversation

LaurentMazare
Copy link
Contributor

TensorFlow bindings for OCaml

The tensorflow-ocaml project provides some OCaml bindings for TensorFlow, a machine learning framework.
These bindings are in an early stage of their development. Some operators are not supported and the API is likely to change in the future. You may also encounter some segfaults. That being said they already contain the necessary to train a convolution network using various optimizers.



Pull-request generated by opam-publish v0.3.1

@camelus
Copy link
Contributor

camelus commented Mar 31, 2016

✅ All lint checks passed 6f548c5
  • These packages passed lint tests: tensorflow-ocaml.0.0.1

✅ Installability check (4736 → 4737)
  • new installable packages (1): tensorflow-ocaml.0.0.1

"ctypes" {>= "0.5"}
"ctypes-foreign"
"ocamlfind"
"ocamlbuild"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ocamlfind and ocamlbuild can be marked as {build} dependencies in the future. This helps reduce the recompilation burden on users when those packages are updated.

@dsheets
Copy link
Member

dsheets commented Mar 31, 2016

Thanks for the bindings! Really cool!

@dsheets dsheets merged commit 101ebb3 into ocaml:master Mar 31, 2016
@LaurentMazare
Copy link
Contributor Author

Thanks for the quick merge! I'll make the change you suggested for the next version.

@agarwal
Copy link
Member

agarwal commented Apr 1, 2016

Isn't the recommendation to drop the "ocaml" from OPAM packages in most cases. This repo is all about OCaml, so using "ocaml" in a package name is almost always redundant.

As a much more minor point, the git project names for bindings to a library foo are pretty much always called ocaml-foo, not foo-ocaml.

@dsheets
Copy link
Member

dsheets commented Apr 1, 2016

@agarwal you are right -- I missed the -ocaml. I have filed ocaml-opam/Camelus#10 for automating this check.

@LaurentMazare could you please rename your opam package? We don't mind about the name of the repository or tarball but we generally try to keep the namespace free of ocaml unless there is a good justification. Sorry for my oversight!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants