Skip to content

re-add editables to dependencies#67

Merged
wolfv merged 2 commits intoconda-forge:mainfrom
pavelzw:patch-1
Jan 5, 2026
Merged

re-add editables to dependencies#67
wolfv merged 2 commits intoconda-forge:mainfrom
pavelzw:patch-1

Conversation

@pavelzw
Copy link
Copy Markdown
Member

@pavelzw pavelzw commented Jan 4, 2026

Updated build number and modified requirements.

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.

editables for some reason is not a strict requirement of hatchling (and not even mentioned as an extra dependency? they mention it in the code: https://github.com/pypa/hatch/blob/025f9c9c2fe54b806ff73adafe5916fa713d4cf0/backend/src/hatchling/builders/constants.py#L43) but it is still needed for editable installations.

i think editable installations are a use case that should be handled by the default build backend and that it should be part of the default package.
otherwise you would need to patch every conda/pixi project where you are running pip install -e . (before, it was supported)

@pavelzw
Copy link
Copy Markdown
Member Author

pavelzw commented Jan 4, 2026

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Copy Markdown
Contributor

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

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

For recipe/recipe.yaml:

  • ℹ️ No valid build backend found for Python recipe for package hatchling 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/20691201738. Examine the logs at this URL for more detail.

@conda-forge-admin
Copy link
Copy Markdown
Contributor

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

@conda-forge-admin
Copy link
Copy Markdown
Contributor

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/conda-forge-webservices/actions/runs/20691205000. Examine the logs at this URL for more detail.

@conda-forge-admin
Copy link
Copy Markdown
Contributor

conda-forge-admin commented Jan 4, 2026

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

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

For recipe/recipe.yaml:

  • ℹ️ No valid build backend found for Python recipe for package hatchling 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/20696608479. Examine the logs at this URL for more detail.

Updated build number and modified requirements.
@pavelzw
Copy link
Copy Markdown
Member Author

pavelzw commented Jan 4, 2026

@conda-forge/hatchling this is ready for review

cc @bollwyvl

@pavelzw pavelzw mentioned this pull request Jan 4, 2026
11 tasks
@bollwyvl
Copy link
Copy Markdown
Contributor

bollwyvl commented Jan 4, 2026 via email

kbseah added a commit to kbseah/phyloblitz that referenced this pull request Jan 5, 2026
Required by hatchling for editable installations, but an upstream change
to the hatchling conda-forge recipe broke this.

See conda-forge/hatchling-feedstock#67
@wolfv wolfv merged commit 68c0d5a into conda-forge:main Jan 5, 2026
4 checks passed
@pavelzw pavelzw deleted the patch-1 branch January 5, 2026 10:30
@wolfv
Copy link
Copy Markdown
Member

wolfv commented Jan 5, 2026

Thanks @pavelzw!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants