Update feedstock to match PyNE conda build

[bquan0]

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.

Now that PyNE has a working conda build, this PR will update the PyNE feedstock so that the updated PyNE version can be installed from conda. Changes include:

• replacing nose with pytest
• adding DAGMC as a dependency that PyNE can be installed with
• updating the github source to the develop branch
• adding dependencies that PyNE needs (according to the conda build in PyNE)

[conda-forge-webservices]

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:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [73]
• 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.

[conda-forge-webservices]

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.

[gonuke]

@conda-forge-admin, please rerender

[bquan0]

@conda-forge-admin, please rerender

[gonuke]

As far as I can tell, this seems to be failing with the way that nuc_data_make is being called. I can't tell why, but it might be interesting to take that out of the build script just to see if it makes things work?

Notably, we used to explicitly call the python interpretter - maybe we should still?

${PYTHON} ${PREFIX}/bin/nuc_data_make

[gonuke]

I think this is where things are failing right now. Not sure why and/or if we need to do it the old way?

[gonuke]

I see you haven't yet updated the dependency list in the meta.yml. You did a bunch of work in pyne/pyne to get those right, but they aren't included here. It's currently failing on progress but maybe there will be others.

[conda-forge-webservices]

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:

• Recipes should usually depend on matplotlib-base as opposed to matplotlib so that runtime environments do not require large packages like qt.

[bquan0]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/pyne-feedstock/actions/runs/10290124810.

[conda-forge-webservices]

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.

[bquan0]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/pyne-feedstock/actions/runs/10409812964.