Closed marcelm closed 1 year ago
One more point: It would be good to state the license explicitly. There is a LICENSE file with the GPL 3, but some projects use "GPL 3 or later" and some use "GPL 3 only". (There are two different SPDX license identifiers "GPL-3.0-only" and "GPL-3.0-or-later".)
Note that using the GPL may mean that some people may refrain from using your software as it has a "viral" aspect. (As derived works also need to be licensed under the GPL 3.) You could choose a simple permissive license such as the MIT license to avoid this. If you’re aware of this aspect, please don’t see this as criticism of your choice of license; I just wanted to point out what it means in case you were not aware of the implications.
Hey @marcelm, Thanks for going over salty. Regarding the license we are happy to keep the existing language. Thanks for checking. All the other comments have been addressed. Cheers, Liam
Great! Nice I was able to help.
Hi, I was looking at your Bioconda recipe PR for this package and noticed a couple of minor things not directly related to the recipe, but to the tool, which I wanted to list here.
python setup.py install
to install a package is deprecated. You should change the installation instructions to usepip install .
instead (usepip install -e .
during development for an editable install).python salty.py
, but this works only if run from thesalty/
subdirectory. You specified insetup.py
that asalty
binary is to be installed, and that is also what the Bioconda recipe tests. I suggest to use justsalty
for consistency.pyproject.toml
for declaring project metadata and get rid ofsetup.py
entirely. See this example. This is the modern way to do packaging. :smile:-c conda-forge -c bioconda --strict-channel-priority
.