Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 29 22:18
    rt121212121 labeled #3801
  • Jan 29 22:18
    rt121212121 labeled #3801
  • Jan 29 22:18
    rt121212121 opened #3801
  • Jan 28 22:04
    pradyunsg commented #3772
  • Jan 28 22:04
    pradyunsg commented #3772
  • Jan 28 17:59
    jaraco commented #3790
  • Jan 28 17:58

    jaraco on main

    Bump version: 66.1.1 → 67.0.0 (compare)

  • Jan 28 17:58

    jaraco on v67.0.0

    (compare)

  • Jan 28 15:11
    jaraco commented #2788
  • Jan 28 14:41
    amol- commented #2788
  • Jan 28 14:10
    dvzrv commented #3790
  • Jan 27 18:11
    kozmaz87 commented #3772
  • Jan 27 18:08
    xkszltl commented #3772
  • Jan 27 18:06
    kozmaz87 commented #3772
  • Jan 27 18:05
    xkszltl commented #3772
  • Jan 27 17:56
    kozmaz87 commented #3772
  • Jan 27 17:53
    kozmaz87 commented #3772
  • Jan 27 17:53
    kozmaz87 commented #3772
  • Jan 27 17:51
    kozmaz87 commented #3772
  • Jan 27 17:36
    xkszltl commented #3772
Paul Ganssle
@pganssle
Did you have to sign something? Was there a fixed term?
Like if you wanted to drop tidelift sponsorship, is there a notice period?
Jason R. Coombs
@jaraco
I’d have to get back to you on that. I’m 80% confident there’s no notice period longer than 30 days.
Paul Ganssle
@pganssle
OK. I may need to ask my work if there are any problems with this. I doubt it, but the rules about appearances are weird.
Not that you'd have to stop taking money, but they may have a problem with me being associated with a project that's nominally for profit.
Probably not, though. It would be pretty weird if I couldn't work on it just because someone else is getting paid to work on it.
Jason R. Coombs
@jaraco
Understandable.
And honestly, your contribution is more valuable than the funding on the project, so if there is an issue, I’d want to seek another arrangement.
The notice period is 30 days.
Paul Ganssle
@pganssle
Sounds good.
Jason R. Coombs
@jaraco
Perhaps you and Benoit would be available for a call this Friday or weekend to discuss.
Paul Ganssle
@pganssle
Sure. I'm at PyCon CA at the moment. I dunno if you saw my pypa-commiters post.
Jason R. Coombs
@jaraco
I did not; would you send me a link?
Paul Ganssle
@pganssle
We're sorta getting our heads around writing a bot that would use this or something similar: https://github.com/gvalkov/setuptools-py2cfg
Start facilitating people in moving from setup.py to setup.cfg.
Jason R. Coombs
@jaraco
Nice! I’ve been doing the same manually for a number of my projects.
@pganssle I don’t know if I’m on pypa-committers. I may not be.
Jason R. Coombs
@jaraco
And looking at the mailing list, I don’t see your post.
Paul Ganssle
@pganssle
The internet here is not great, I think it didn't go through.
I may need to go over to the Bloomberg office.
Jason R. Coombs
@jaraco
:)
Paul Ganssle
@pganssle
Weird, it's in my sent list.
Maybe the mailman 3 migration screwed it up.
Paul Ganssle
@pganssle
Uggggh.
Pushed an erroneous tag.
Deleted it.
Anyway, I've tagged the 40.6.0 release.
Paul Ganssle
@pganssle
Jason R. Coombs
@jaraco
I’ve seen Travis jobs fail when a ref is pulled.
Paul Ganssle
@pganssle
I think I found the issue.
I think ! has some special meaning either in travis or in YAML.
Like it means "execute this line", not "invert the meaning of this line"
Jason R. Coombs
@jaraco
Oh, yeah. Maybe “execute this line but continue if it fails"
Paul Ganssle
@pganssle
Well, it's breaking on that, so it can't be that.
The actual log says $ grep pyc setuptools.egg-info/SOURCES.txt
Jason R. Coombs
@jaraco
I remember that PR.
Paul Ganssle
@pganssle
So I think it's getting interpreted as "execute grep pyc ..." instead of "execute ! grep pyc ..."
Should I delete and re-create the 40.6.0 tag with the release script fixed?
Jason R. Coombs
@jaraco
Yes.
Since the release never went out, I consider it safe (within a few hours) to replace the tag.
Paul Ganssle
@pganssle
Yeah, I agree.
Ralf Weber
@RJMW
pypa/setuptools#232 Please, any progress on Issue 1 in this post? I am struggling to find a way to install the requirements when cmdclass and install is included in setup.py. Workaround?
Paul Ganssle
@pganssle
I'm not sure I understand that issue. Hard to know why
Paul Ganssle
@pganssle
Sorry, that should have said "Hard to know how to work around this issue without knowing what you need to do" @RJMW
Stephan Steinbach
@ssteinbach
Hello, is there a good way to figure out the minimum version of setuptools my project requires? At the moment the problematic fields seem to be project_urls and tests_require
Jason R. Coombs
@jaraco
@ssteinbach I’m pretty sure tests_require has been around a very long time. I’m less sure about project_urls. You can refer to the history, which may or may not make mention of that particular change.
Thomas Robitaille
@astrofrog
Hi all, I'm updating some of my packages to use the declarative setup.cfg way of specifying package options instead of listing them in setup.py. But I was just curious as to what the plan is for future in terms of setup.cfg vs pyproject.toml - is the long term plan to have everything declared in pyproject.toml instead of setup.cfg?