Adding conda package for drug2cell tool

[Mennayousef]

I am attempting to create a conda recipe package for drug2cell tool.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/drug2cell/meta.yaml) and found some lint.

Here's what I've got...

For recipes/drug2cell/meta.yaml:

• ❌ There are too few lines. There should be one empty line at the end of the file.
• ❌ requirements: host: python >= 9999 should not contain a space between relational operator and the version, i.e. python >=9999
• ❌ requirements: run: python >= 9999 should not contain a space between relational operator and the version, i.e. python >=9999

For recipes/drug2cell/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
  • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12074817681. Examine the logs at this URL for more detail.}

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

File-specific lints and/or hints:

• recipes/drug2cell/meta.yaml:
  • lints:
    • The following maintainers have not yet confirmed that they are willing to be listed here: mennayousef. Please ask them to comment on this PR if they are.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/drug2cell/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/drug2cell/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12074840935. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/drug2cell/meta.yaml) and found some lint.

Here's what I've got...

For recipes/drug2cell/meta.yaml:

• ❌ The recipe must have some tests.

For recipes/drug2cell/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12075053995. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/drug2cell/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/drug2cell/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12075173996. Examine the logs at this URL for more detail.}

[mfansler]

Thanks for spending time on this! Unfortunately, I'm not for merging this as it stands.

Conda Forge packages should be properly versioned, either through PyPI or GitHub Releases rather from a commit hash, which is mutable. My recommendation is either that one gets the lab to commit to making releases of some form, or instead move this to Bioconda, which aligns with the intent of the package and also has a lower bar for recipe standards.

[mfansler]

Just noticed that this was merged on Bioconda (bioconda/bioconda-recipes#52452). As a noarch recipe, there will not be any advantage to shifting to Conda Forge, even with the version issue addressed. As such, I will close this.