CLI proposal: Rename `develop` into `install`, remove `develop`
See original GitHub issueWith the introduction of poetry develop
, poetry install
seems redundant. Both commands install the deps, but develop
also makes the package importable from any script executed with poetry run
. It seems install
is just a worse version of develop
now.
Making this change will simplify the CLI, reduce confusion (install
command would install the package), all without breaking the current poetry install
behavior.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:10 (8 by maintainers)
Top Results From Across the Web
How do I rename both a Git local and remote branch name?
Go to the web page create PR in GH, you will see the new branch as well as the old branch 6. Back...
Read more >Add a command to rename default branches #1215 - GitHub
Describe the feature or problem you'd like to solve It takes at least three to five steps to rename the default branch of...
Read more >How to rename a local and remote Git branch - IONOS
To do this, use the following command: “git push origin --delete old-name”. Verify that the old branch has been deleted properly. Now add...
Read more >Easily rename your Git default branch from master to main
Go to the master branch; Rename master to main locally; Get the latest commits from the server; Remove the link to origin/master; Add...
Read more >How to rename and change a Git branch name locally &
Rename the Git branch locally with the git branch -m new-branch-name command; Push the new branch to your GitHub or GitLab repo; Delete...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@cauebs I’m sorry you feel that way. That was not my intention. Be assured that I value every feedback and I try to be as responsive as possible. So even though I do not necessarily respond it does not mean that I am not taking into account the feedback people are giving.
Specifically for this issue, the introduction of
develop
was a poorly though out idea and this issue made me aware of it. However, more important issues required my attention and, in the end, I put it on the backlog but I kept it in the back of my mind. And once the bulk of the work for release0.12.0
was done I found the time to address this without notifying the participants and telling them that this concern had been heard and that it was being taken care of.This is poor communication on my part, I agree, but rest assured that I welcome any discussion that can lead to improving Poetry.
@sdispater could you weight in on this proposal when you have time?