Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix linting complaints and update to v0.5.2 #7

Closed

Conversation

apjanke
Copy link

@apjanke apjanke commented May 31, 2024

Checklist

  • Used a fork of the feedstock to propose changes
  • [n/a] 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. (I don't know how to do this; sorry.)

This should close the outstanding version bump PRs and bump-request issues:

Closes #6
Closes #5
Closes #4

This hopefully fixes the linter check falures that are causing the outstanding PRs for 0.5.2 and previous version bumps to fail their tests. Maybe that's what has prevented them from getting merged, and this PR will get an 0.5.2 upgrade going. We'd like to use fredapi 0.5.2 at our work because the current 0.4.2 version in this conda-forge package is not compatible with Python 3.11, due to a change in the xml package's API.

These are the outstanding PRs I see currently. I think getting this 0.5.2 upgrade through will make all of them moot.

image

I see them failing with the following linter complaints, which I believe this PR will fix:

image

This addresses a conda-forge-webservices linter complaint ("License is not an SPDX identifier...") showing up as a check failure in PRs like conda-forge#6.
@conda-forge-webservices
Copy link

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) and found some lint.

Here's what I've got...

For recipe:

  • requirements: host: python>=3.2 must contain a space between the name and the pin, i.e. python >=3.2
  • requirements: run: pandas>=0.15 must contain a space between the name and the pin, i.e. pandas >=0.15
  • requirements: run: python>=3.2 must contain a space between the name and the pin, i.e. python >=3.2
  • noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

apjanke added 3 commits May 31, 2024 16:33
This fixes a linter complaint ("noarch: python recipes are required to have a lower bound on the python version") that's showing up in PRs like conda-forge#6.

I'm not sure if the python 3.2 lower bound is actually correct. The fredapi package's contents itself do not specify a minimum Python version in the documentation or metadata, as far as I can see. I selected 3.2 because that's the minimum version required by pandas 0.15, and the fredapi package does declare a 'pandas>=0.15' dependency in its requirements.txt.
@apjanke apjanke force-pushed the fix-linting-complaints-and-0.5.2 branch from 6bcb77f to 1cd9d07 Compare May 31, 2024 20:33
@conda-forge-webservices
Copy link

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

@apjanke apjanke changed the title Fix linting complaints and update to 0.5.2 Fix linting complaints and update to v0.5.2 May 31, 2024
@adament adament mentioned this pull request Dec 3, 2024
5 tasks
@ocefpaf ocefpaf closed this in #12 Dec 3, 2024
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.

@conda-forge-admin, please update version
1 participant