- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 218
 
          Packaging: Use versioningit for maintaining the package version
          #535
        
          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
base: main
Are you sure you want to change the base?
Conversation
| 
          
 Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the  You can disable this status message by setting the  Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit: 
 Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
 Other keywords and placeholders
 CodeRabbit Configuration File (
 | 
    
b11187e    to
    dc13b94      
    Compare
  
    1033e3c    to
    f64a7ba      
    Compare
  
    86456fc    to
    7df6d17      
    Compare
  
            
          
                docs/source/conf.py
              
                Outdated
          
        
      | 
               | 
          ||
| project = "responder" | ||
| copyright = "2018, A Kenneth Reitz project" | ||
| copyright = "2018-2024, A Kenneth Reitz project" | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i typically just add the current year and keep it up to date
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
        
          
                setup.py
              
                Outdated
          
        
      | os.system("dpkg-buildpackage -rfakeroot -uc -us") | ||
| 
               | 
          ||
| 
               | 
          ||
| class UploadCommand(Command): | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I use this on all my projects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hear you. However, I think package authors gradually need to modernize.
setup.py-based commands are being deprecated by setuptools and friends, at some time setup.py per se might also become deprecated, and in general, pyproject.toml-based project metadata tech is mature, even without special tooling (just setuptools), it will be the future and it is here to stay.
In this spirit, project metadata will not be able to include procedural/imperative steps natively any longer. I think it makes sense to accompany modernizations in the Python ecosystem, and will be happy to support you in getting back your loved sandbox workflows based on modern utilities, based on curated recipes we have been crafting on other projects we are maintaining.
Effectively, it will just be another incantation command to remember, for example poe upload or poe build-deb. I think it will be easy to adjust, and you may want to reuse the recipes you like also on your other projects when modernizing them.
If you agree, let's do that on behalf of this project and the next iterations. If you disagree, let's close this PR again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i have mixed feelings, but I'm not opposed. Let's just document the procedures for making a release, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks again for the help
| 
           got some nasty merge conflicts on this one. i'm down to merge though, once resolved  | 
    
        
          
                responder/__init__.py
              
                Outdated
          
        
      | from . import ext | ||
| from .core import API, Request, Response | ||
| 
               | 
          ||
| __appname__ = "responder" | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've never seen __appname__ before. What's this from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably just a stray pickup. We can also remove it again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed.
392e30f    to
    84a2fdc      
    Compare
  
    The Debian package builder has been saved to `bin/mkdeb.py` for now. It needs to be refurbished into a `poethepoet` task subsequently.
| 
           While I've used it like this before, I currently can't get  ValueError: Could not parse `git describe` output-- https://github.com/kennethreitz/responder/actions/runs/11518104403/job/32064158112?pr=535#step:5:22 Let's postpone this patch to a later iteration, after migrating to a pure   | 
    
About
pyproject.toml, phase out the Debian package builder to a dedicated utility programbin/mkdeb.py. It can be hooked into a corresponding poethepoet task afterwards, to improve invocation convenience if you need it.Status
This patch is also stacked upon GH-532, so its merge order is currently on the last position of the synthetic merge queue.