Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Bump version to 0.5.2 and prepare for PyPI release

Open
#148 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
python, scikit-learn

Research direction

Open setup.py at line 35 and verify the current package version and release metadata before making the requested version change. Confirm the version is 0.5.2, run python -m build, and verify the resulting distribution is ready for the maintainer to publish to PyPI.

Written by the indexing model from the issue text.

Description

Summary
This PR bumps the version from 0.5.1 to 0.5.2 to prepare for a PyPI release that includes the critical scikit-learn 1.6+ compatibility fix.

Problem
The current PyPI release (v0.5.1, February 2024) contains deprecated force_all_finite parameters that cause TypeError with scikit-learn 1.8+:

TypeError: check_array() got an unexpected keyword argument 'force_all_finite'.
Did you mean 'ensure_all_finite'?
Fix Status
The fix was committed on January 21, 2025 (commit de933d2) by @sateeshm and merged by @desilinguist. The fix:

Replaced all force_all_finite with ensure_all_finite in factor_analyzer.py and confirmatory_factor_analyzer.py
Updated requirements to scikit-learn>=1.6.0
The fix exists in main but has never been released to PyPI (7+ months).

User Impact
Users with scikit-learn 1.8+ cannot use factor_analyzer from PyPI. They must use the workaround:

pip install git+https://github.com/EducationalTestingService/factor_analyzer.git
Related Issues
#147 - "Factor_analyzer now is broken" (Jan 13, 2026)
#142 - "Push changes to pypi" (Jun 7, 2025) - no maintainer response
#145 - FutureWarning still present in PyPI version
What This PR Does
Bumps version from 0.5.1 to 0.5.2 in setup.py
What Needs to Happen Next
After this PR is merged, a maintainer needs to:

Create a GitHub release:

git tag -a v0.5.2 -m "Release v0.5.2 - scikit-learn 1.8+ compatibility"
git push origin v0.5.2
Build and publish to PyPI:

python -m build
python -m twine upload dist/*
Files Changed
setup.py: Version bump from 0.5.1 to 0.5.2
Testing
Tested with:

Python 3.14
scikit-learn 1.8.0
Installation from GitHub main branch works correctly
Code Change
In setup.py, change line 35:

OLD

version="0.5.1"

NEW

version="0.5.2"
Note for maintainers: If you need help with the PyPI release process or don't have publish access anymore, please let the community know. Several users have offered to help test and assist with the release.

Dominant language
Python
Stars
6
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EducationalTestingService/factor_analyzer

All issues in EducationalTestingService/factor_analyzer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.