Did you have to sign something? Was there a fixed term?
Like if you wanted to drop tidelift sponsorship, is there a notice period?
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.
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.
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.
@pganssle I don’t know if I’m on pypa-committers. I may not be.
I may need to go over to the Bloomberg office.
Pushed an erroneous tag.
Deleted it.
Anyway, I've tagged the 40.6.0 release.
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"
The actual log says
$ grep pyc setuptools.egg-info/SOURCES.txt
Should I delete and re-create the 40.6.0 tag with the release script fixed?
Yes.
Since the release never went out, I consider it safe (within a few hours) to replace the tag.
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?
@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.