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

New release on Pypi #1635

Open
Tomo59 opened this issue Mar 20, 2024 · 5 comments
Open

New release on Pypi #1635

Tomo59 opened this issue Mar 20, 2024 · 5 comments
Labels

Comments

@Tomo59
Copy link
Contributor

Tomo59 commented Mar 20, 2024

Hello, could you do a new release on pypi ? It's been more than a year now and there have been several bugfixes included in main branch since then.

Thanks.

Thomas.

@sbraz
Copy link
Contributor

sbraz commented Apr 25, 2024

Hi, I second this request. The latest release has a lot of warnings that were fixed in git like DeprecationWarning: unittest.findTestCases() is deprecated and will be removed in Python 3.13..

@mnaberez
Copy link
Member

The latest release has a lot of warnings that were fixed in git like DeprecationWarning: unittest.findTestCases() is deprecated and will be removed in Python 3.13.

Yeah, looks like that was fixed 49b74ca, just a couple days after 4.2.5 was released to PyPI.

@JKrehling
Copy link

Theres been some CPU fixes too, 2a93d6b

What would be needed to get a 4.3.0 or a 4.2.6 release on pypi?

@whatnick
Copy link

Perhaps a concrete action here would be to create a PR for pypi release from GitHub actions to reduce the manual load on the maintainers. That way a tag can create a release (at least a dev one on test.pypi).

@dkebler
Copy link

dkebler commented Oct 1, 2024

It has been almost two years of commits since 4.2.5. Not sure if I need them but I only like to use projects that are relatively up to date and active. This project is active but the release is out of date. I assume there is something like a stable release in these commits somewhere. Not really knowing which commit I decided to just clone the latest commit and run that to see assumming all the commits are vetted/tested.

On alpine (in docker container image) I did this.

first install the supervisor package
then (in dockerfile) can run this

update_supervisor  () {
supver=$(/usr/bin/supervisord --version)
pkgs=/usr/lib/python3.12/site-packages
echo updating supervisord $supver to latest commit from https://github.com/Supervisor/supervisor.git
mv $pkgs/supervisor $pkgs/supervisor-$supver 
git clone https://github.com/Supervisor/supervisor.git /tmp/supervisor
mv /tmp/supervisor/supervisor $pkgs/supervisor
if [[ $(/usr/bin/supervisord --version) == *dev* ]]; then
  echo supervisord has been updated to latest commit 
  /usr/bin/supervisord --version
  rm -rf  /tmp/supervisor
  rm -rf $pkgs/supervisor-$supver
  else
  unable to update supervisord, rolling back to latest release $supver
  rm -rf $pkgs/supervisor
  mv $pkgs/supervisor-$supver $pkgs/supervisor
  if [[ $(/usr/bin/supervisord --version) == "$supver" ]]; then 
    echo restore succesfull
   else
     echo WARNING: restore failed
     return 1 
  fi
fi
}

update_supervisor

If the maintainers ask for some help maybe we can assist with clearing/closing all the old issues and assuming this repo is not just a mirror making a CI for a stable/dev releases. I figure the alpine package generator is only waiting on a new stable tag/release and then we would see the new version in the package so that's why it's so stale at this point.

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

No branches or pull requests

6 participants