What is the difference between - baml-py - baml It appears to be a legacy app, and i think should be removed. I think we only need

baml-py

and nothing else. Would it be possible for the maintainers to remove `baml`; `baml-cli`;

baml-lib

and those unnecessary packages as it is confusing and not maintained My suggestion would be rename

baml-py

to

baml

as per the naming convention followed in other languages (typescript/go etc). https://cdn.discordapp.com/attachments/1253172394345107466/1468885453401751572/image.png?ex=6985a5ae&is=6984542e&hm=bd43557968d306218d11624493f69023d84542807a4c759ed750abb35c0bca55&

This is a topic that has come up multiple times over the last years. IIRC, boundary owns the baml namespace in PyPI but I think now baml-py is used in so many dependency files and CI workflows that it might require engineering time and a deprecation cycle to move to the baml namespace. Also, does PyPI support aliasing package names (can baml-py coexist with baml?) not sure 🤔

My take would be to make those changes now as it still not widely adopted than have it later when the changes would be almost impossible. Take the example of

pip install python-dotenv

(Why just WHY) . Moreover PyPI will have python packages, there is no need to have a

prefix

or

suffix

Agreed, baml is just so much easier to type than baml-py