You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--pkg-name PKG_NAME package name of the created package
--pkg-version PKG_VERSION
package version of the created package
--pkg-build PKG_BUILD
package build number of the created package
The text was updated successfully, but these errors were encountered:
@ilanschnell Could you please add a note to this issue about how one should use recipes to get the equivalent behaviour of conda pip --pkg-name etc. as this is not yet clear from the documentation. (This note should probably also be added to the deprecation message for the pip command.)
@mforbes That depends which part of the conda pip you are interested in. If you just want to install a package using pip, then just use pip directly. If you want to create a package (also for others to use), then "conda build" is the command to use, which gives much better control over how the conda-package is build, and optionally it can be uploaded to binstar.org.
The "conda pip" command has been deprecated because of several reasons:
We added "conda build" in version 1.7
It does two many things at once (builds and installs a conda-package)
Is too Python specific (conda is a Python agnostic packaging tool)
It is confusing, i.e. it makes people believe that using pip directly not possible
Just like conda package:
The text was updated successfully, but these errors were encountered: