Log file Viewer

[14:24:05] <ronny> lifeless: ping?

[14:25:19] <ronny> lifeless: wondering if we could shedule a basic discussion wrt pbr/setuptools_scm/setuptools in the next 1-2 weeks

[17:24:49] <lifeless> ronny: sure

[17:25:05] <lifeless> ronny: needs to be next week, or after the openstack tokyo summit

[19:47:36] <Ivo> qwcode, maybe not include testing py26 in tox?

[19:47:48] <Ivo> Small part in getting people to at least use 2.7..

[19:48:31] <qwcode> Ivo, yea, I just know py26 can be an outlier for distutils and MANIFEST.in, so I wanted to include it

[19:49:06] <qwcode> IDK. I guess I don't care

[19:59:30] <Ivo> qwcode, with latest setuptools version it'd now be legit to run `python setup.py test` in tox.ini, instead of just package checking

[19:59:53] <qwcode> Ivo, I have another PR coming for that

[20:00:21] <Ivo> otherwise you could add testsuite keyword to setup.py for older setuptools versions

[20:02:23] <qwcode> I think using "setup.py test" is pretty alien to most people. I'm switching to pytest, but not because we're endorsing it....

[20:02:37] <Ivo> alien to most people?

[20:03:06] <Ivo> I didn't know so :D

[20:03:55] <Ivo> nose people might not like that...

[20:06:57] <qwcode> again, we're not endorsing it... using "setup.py test" involved adding something to setup.py (test_suite) that we then have to explain... so that bothered me...

[20:08:30] <ionelmc> qwcode: does the sampleproject get any traffic?

[20:09:20] <qwcode> ionelmc, it's linked in many places in the Packaging User Guide. it comes up on distutils-sig from time to time

[20:09:57] <qwcode> it has 169 forks

[20:11:26] <Ivo> dstufft, seen any progress from apple?

[20:11:33] <ionelmc> qwcode: makes one wonder if it's actually doing any good, one of the cookiecutter templates has 315forks

[20:11:52] <Ivo> qwcode, if you have setuptools 18.4 yuou don't have to add anything to setup.py :D

[20:12:21] <Ivo> well the cookiecutter people advertise themselves in places often

[20:12:24] <qwcode> Ivo, whatever, do you really want to see "python setup.py test" instead of "pytest"?

[20:12:52] <qwcode> ionelmc, it only ever existed for ease in writing the packaging tutorial.

[20:13:05] <ionelmc> well anyway

[20:13:07] <Ivo> IMHO yes

[20:13:20] <Ivo> we don't advertise sampleproject much do we

[20:14:13] <ionelmc> i think you should rename the guide to reference :|

[20:14:21] <Ivo> I guess it's linked early on in distributing page of packaging.python.org

[20:15:03] <ionelmc> cause that ain't no guide, it has too many details

[20:15:05] <Ivo> packaging.python.org is still kinda young tho, hopefully it can help a lot more people in time to come

[20:17:06] <qwcode> Ivo, it's years old actually : )

[20:17:44] <Ivo> compared to https://docs.python.org/2.7/distutils/index.html tho?

[20:17:46] <Ivo> :P

[20:18:03] <qwcode> true

[20:18:46] <Ivo> I also like `python setup.py test` in that it lets you write any underlying testing mechanism (unittest, pytest, nose) under it, but has the same simple command

[20:51:31] <qwcode> ionelmc, but really, it's not meant to be forked. it's meant to be looked thru while going thru the PyPUG section on "Packaging and Distributing Projects"

[20:55:03] <ionelmc> qwcode: doesn't that mean people use it as a template?

[20:56:44] <qwcode> ionelmc, looking at it, doesn't mean "template"

[20:56:56] <qwcode> certainly not like a cookiecutter template

[20:58:25] <qwcode> cookiecutter is good for giving you all the stuff you need for a project... whereas we don't want to be authorities on all that... and start debates on things we're not trying to cover

[20:58:56] <qwcode> like setup.py test vs pytest vs nose

[20:59:47] <qwcode> i.e. I didn't want to just give snippets in the PyPUG tutorials