Adding `smolagents` from PyPI #28741

sugatoray · 2025-01-02T19:35:45Z

Checklist

github-actions · 2025-01-02T19:37:05Z

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

conda-forge-admin · 2025-01-02T19:37:27Z

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/smolagents/meta.yaml) and found it was in an excellent condition.

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

For recipes/smolagents/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/12587776214. Examine the logs at this URL for more detail.}

conda-forge-admin · 2025-01-03T03:41:47Z

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/smolagents/meta.yaml, recipes/e2b-code-interpreter/meta.yaml, recipes/e2b/meta.yaml) and found some lint.

Here's what I've got...

For recipes/smolagents/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).

For recipes/e2b-code-interpreter/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).

For recipes/e2b/meta.yaml:

❌ There are too few lines. There should be one empty line at the end of the file.
❌ Recipe maintainer "ADD_YOUR_GITHUB_ID_HERE" does not exist

For recipes/e2b/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/12592401613. Examine the logs at this URL for more detail.}

github-actions · 2025-01-03T03:42:19Z

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

File-specific lints and/or hints:

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

github-actions · 2025-01-03T03:44:14Z

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

conda-forge-admin · 2025-01-03T03:44:20Z

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/duckduckgo-search/meta.yaml, recipes/smolagents/meta.yaml, recipes/e2b-code-interpreter/meta.yaml, recipes/primp/meta.yaml, recipes/e2b/meta.yaml) and found it was in an excellent condition.

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

For recipes/duckduckgo-search/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).

For recipes/smolagents/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).

For recipes/e2b-code-interpreter/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).

For recipes/primp/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).

For recipes/e2b/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/12593843540. Examine the logs at this URL for more detail.}

sugatoray · 2025-01-03T04:04:38Z

Build Failure Reason

See source: Error Line #1364-#1370

🔥 The error happens while building for e2b_code_interpreter.

Could not solve for environment specs
The following packages are incompatible
├─ duckduckgo-search >=6.3.7 * does not exist (perhaps a typo or a missing channel);
├─ gradio >=5.8.0 * is installable and it requires
│  └─ python-multipart >=0.0.18 *, which can be installed;
└─ litellm >=1.55.10 * is not installable because it requires
   └─ python-multipart >=0.0.9,<0.0.10 *, which conflicts with any installable versions previously reported.

conda-forge-admin · 2025-01-03T06:39:29Z

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

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

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

conda-forge-admin · 2025-01-03T06:49:44Z

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/primp/meta.yaml, recipes/e2b-code-interpreter/meta.yaml, recipes/smolagents/meta.yaml, recipes/duckduckgo-search/meta.yaml, recipes/e2b/meta.yaml) and found it was in an excellent condition.

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

For recipes/primp/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).

For recipes/e2b-code-interpreter/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).

For recipes/smolagents/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).

For recipes/duckduckgo-search/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).

For recipes/e2b/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/12593943037. Examine the logs at this URL for more detail.}

conda-forge-admin · 2025-01-05T03:43:41Z

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/primp/meta.yaml, recipes/duckduckgo-search/meta.yaml, recipes/smolagents/meta.yaml) and found some lint.

Here's what I've got...

For recipes/primp/meta.yaml:

❌ Non noarch packages should have python requirement without any version constraints.
❌ Non noarch packages should have python requirement without any version constraints.

For recipes/duckduckgo-search/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).

For recipes/smolagents/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/12657414098. Examine the logs at this URL for more detail.}

github-actions · 2025-01-05T03:43:54Z

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

It looks like some changes were made outside the recipes/ directory. To ensure everything runs smoothly, please make sure that recipes are only added to the recipes/ directory and no other files are changed.

If these changes are intentional (and you aren't submitting a recipe), please add a maintenance label to the PR.

File-specific lints and/or hints:

broken-recipes/skip-recipes/e2b/_meta.yaml:
- lints:
  - Do not edit files outside of the recipes/ directory.
broken-recipes/skip-recipes/e2b-code-interpreter/_meta.yaml:
- lints:
  - Do not edit files outside of the recipes/ directory.
broken-recipes/skip-recipes/e2b/LICENSE:
- lints:
  - Do not edit files outside of the recipes/ directory.
broken-recipes/skip-recipes/e2b-code-interpreter/LICENSE:
- lints:
  - Do not edit files outside of the recipes/ directory.

- update build section

conda-forge-admin · 2025-01-07T18:56:53Z

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/smolagents/meta.yaml) and found it was in an excellent condition.

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

For recipes/smolagents/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/12657935763. Examine the logs at this URL for more detail.}

github-actions · 2025-01-07T19:25:11Z

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

sugatoray · 2025-01-07T19:30:57Z

Other related PRs:

Adding primp from PyPI #28780

Adding smolagents from PyPI

5173d85

sugatoray added 2 commits January 2, 2025 22:40

add recipe for e2b from PyPI

213e651

add recipe for e2b-code-interpreter from PyPI

03f7485

update recipe-maintainer for e2b

590539e

sugatoray changed the title ~~Adding smolagents from PyPI~~ Adding smolagents, e2b-code-interpreter from PyPI Jan 3, 2025

sugatoray mentioned this pull request Jan 3, 2025

Include LICENSE file in package source on PyPI e2b-dev/E2B#526

Open

sugatoray added 3 commits January 3, 2025 01:36

add recipe for duckduckgo-search from PyPI

81bd0ff

add recipe for primp from PyPI

25cb5e3

update recipe for smolagents

e29860b

sugatoray added 2 commits January 3, 2025 01:41

fix typo in smolagents recipe

6af749e

fix typo: recipe smolagents

0173d0b

sugatoray added 2 commits January 4, 2025 22:42

hide recipes

cf7282a

update recipe: primp

962be03

sugatoray added 6 commits January 4, 2025 22:51

move skip-recipes folder

c7d5233

rename recipe file to avoid bulding them

d18db94

update recipe: smolagents

a650da5

update recipe: duckduckgo-search

f5f6dfb

update recipe: smolagents

022ccdd

update recipe: duckduckgo-search

38574da

sugatoray added 2 commits January 7, 2025 13:47

update recipe: primp

adb6fa3

- update build section

update recipe: remove version constraints

6b95578

remove additional recipes

2dab4b7

sugatoray changed the title ~~Adding smolagents, e2b-code-interpreter from PyPI~~ Adding smolagents from PyPI Jan 7, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Adding `smolagents` from PyPI #28741

Adding `smolagents` from PyPI #28741

sugatoray commented Jan 2, 2025

github-actions bot commented Jan 2, 2025

conda-forge-admin commented Jan 2, 2025

conda-forge-admin commented Jan 3, 2025 •

edited

Loading

github-actions bot commented Jan 3, 2025

github-actions bot commented Jan 3, 2025

conda-forge-admin commented Jan 3, 2025 •

edited

Loading

sugatoray commented Jan 3, 2025 •

edited

Loading

conda-forge-admin commented Jan 3, 2025 •

edited

Loading

conda-forge-admin commented Jan 3, 2025

conda-forge-admin commented Jan 5, 2025 •

edited

Loading

github-actions bot commented Jan 5, 2025 •

edited

Loading

conda-forge-admin commented Jan 7, 2025 •

edited

Loading

github-actions bot commented Jan 7, 2025

sugatoray commented Jan 7, 2025

Adding smolagents from PyPI #28741

Are you sure you want to change the base?

Adding smolagents from PyPI #28741

Conversation

sugatoray commented Jan 2, 2025

github-actions bot commented Jan 2, 2025

conda-forge-admin commented Jan 2, 2025

conda-forge-admin commented Jan 3, 2025 • edited Loading

github-actions bot commented Jan 3, 2025

github-actions bot commented Jan 3, 2025

conda-forge-admin commented Jan 3, 2025 • edited Loading

sugatoray commented Jan 3, 2025 • edited Loading

Build Failure Reason

conda-forge-admin commented Jan 3, 2025 • edited Loading

conda-forge-admin commented Jan 3, 2025

conda-forge-admin commented Jan 5, 2025 • edited Loading

github-actions bot commented Jan 5, 2025 • edited Loading

conda-forge-admin commented Jan 7, 2025 • edited Loading

github-actions bot commented Jan 7, 2025

sugatoray commented Jan 7, 2025

Adding `smolagents` from PyPI #28741

Adding `smolagents` from PyPI #28741

conda-forge-admin commented Jan 3, 2025 •

edited

Loading

conda-forge-admin commented Jan 3, 2025 •

edited

Loading

sugatoray commented Jan 3, 2025 •

edited

Loading

conda-forge-admin commented Jan 3, 2025 •

edited

Loading

conda-forge-admin commented Jan 5, 2025 •

edited

Loading

github-actions bot commented Jan 5, 2025 •

edited

Loading

conda-forge-admin commented Jan 7, 2025 •

edited

Loading