update meta.yaml

[mmatera]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[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 (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• ❌ This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

For recipe/meta.yaml:

• ℹ️ No valid build backend found for Python recipe for package mathics3 using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12982187372. 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 (recipe/meta.yaml) and found it was in an excellent condition.

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

For recipe/meta.yaml:

• ℹ️ No valid build backend found for Python recipe for package mathics3 using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12982363612. 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 (recipe/meta.yaml) and found it was in an excellent condition.

[mmatera]

@conda-forge-admin, please rerender

[rocky]

I am glad you are undertaking this!

I looked over the changes and this is a whole new world that I know nothing about. So I can't really offer anything here right now.

[mmatera]

@rocky, I am taking the chance to get this working finally when the release happens in the holidays. The first step it to get Mathics-Scanner on conda-forge. When I get it working, I will try to describe how to do it the next time...

[rocky]

@rocky, I am taking the chance to get this working finally when the release happens in the holidays. The first step it to get Mathics-Scanner on conda-forge. When I get it working, I will try to describe how to do it the next time...

Thanks! Add the instructions somewhere in the releasing section of the developer's guide.

[mmatera]

@conda-forge/help-python Please give me some advice to fix the win_64 build configuration.

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

[rocky]

This should be >= 1.4.1 given that Mathics 8 is used.

[mmatera]

I am update this now. Finally, we have a release in conda-forge!