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
we should probably use v1.2 of poetry instead of v1.1
v1.2 implements some breaking changes to the structure of the pyproject.toml file. I have taken a look at some of the changes and decided that we will probably need them in the future. For example, one of the changes includes the installation of python packages from Github URLs where the package lives within a subdirectory of the repository, like plink-ng. So it would be best if we moved to v1.2 with haste -- before our project grows to a stage where we need to make lots of changes to the pyproject.toml file
you should also update the contributing docs to describe how to install the new poetry version
The text was updated successfully, but these errors were encountered:
trouble is that I'd like to install v1.2 inside of a conda environment but there is no v1.2 in the conda-feedstock yet - although, there has been mention of it
so now the plan is to
fork the feedstock and publish poetry v1.2 to our own conda channel
v1.2 implements some breaking changes to the structure of the
pyproject.toml
file. I have taken a look at some of the changes and decided that we will probably need them in the future. For example, one of the changes includes the installation of python packages from Github URLs where the package lives within a subdirectory of the repository, likeplink-ng
. So it would be best if we moved to v1.2 with haste -- before our project grows to a stage where we need to make lots of changes to thepyproject.toml
fileThe text was updated successfully, but these errors were encountered: