Re: [Twisted-Python] Deprecating subproject packaging

On Wed, Apr 22, 2015 at 2:31 PM, HawkOwl wrote: > > > On 23 Apr 2015, at 01:37, Kevin Horn wrote: > > > > Agreed that this is a good idea, though I'd still like to see NEWS > broken out by "subproject" (or maybe we should say "topic" now?). I don't > care whether it's in the same file or not, b

Re: [Twisted-Python] Deprecating subproject packaging

> On 23 Apr 2015, at 08:01, Glyph wrote: > > One immediate thing I think we should decouple, though, are our native > dependencies. IOCPReactor should remain in Twisted, but iocpsupport should > be a separate, optional dependency, available as an extra. Similarly, > _initgroups, sendmsg, po

Re: [Twisted-Python] Deprecating subproject packaging

> On Apr 22, 2015, at 09:28, Adi Roiban wrote: > So, I think we should: - Deprecate the subproject setup.pys starting with 15.2 and stop packaging subprojects separately as of 16.0 (15.2 in May, 15.3 in July, 15.4 in September, 15.5 in November, 16.0 in January 2016 -

Re: [Twisted-Python] Deprecating subproject packaging

> On 23 Apr 2015, at 01:37, Kevin Horn wrote: > > Agreed that this is a good idea, though I'd still like to see NEWS broken out > by "subproject" (or maybe we should say "topic" now?). I don't care whether > it's in the same file or not, but when a new Twisted release comes out I find > revi

Re: [Twisted-Python] Deprecating subproject packaging

Agreed that this is a good idea, though I'd still like to see NEWS broken out by "subproject" (or maybe we should say "topic" now?). I don't care whether it's in the same file or not, but when a new Twisted release comes out I find reviewing changes much easier if I can think about one "topic" at

Re: [Twisted-Python] Deprecating subproject packaging

>>> So, I think we should: >>> >>> - Deprecate the subproject setup.pys starting with 15.2 and stop packaging >>> subprojects separately as of 16.0 (15.2 in May, 15.3 in July, 15.4 in >>> September, 15.5 in November, 16.0 in January 2016 -- so ~4 releases + 1 >>> major release notice). >>> - Rem

Re: [Twisted-Python] Deprecating subproject packaging

> On 22 Apr 2015, at 19:46, Glyph wrote: > > >> On Apr 22, 2015, at 04:04, HawkOwl wrote: > >> So, I think we should: >> >> - Deprecate the subproject setup.pys starting with 15.2 and stop packaging >> subprojects separately as of 16.0 (15.2 in May, 15.3 in July, 15.4 in >> September, 15.5

Re: [Twisted-Python] Deprecating subproject packaging

On 08:04 am, hawk...@atleastfornow.net wrote: Hi, I think that Twisted should deprecate subproject packaging You probably won't hear much if any disagreement with this proposal on this list. The sub-projects were never for people who like and are into Twisted. They were a tool to help conv

Re: [Twisted-Python] Deprecating subproject packaging

> On Apr 22, 2015, at 04:04, HawkOwl > wrote: > So, I think we should: > > - Deprecate the subproject setup.pys starting with 15.2 and stop packaging > subprojects separately as of 16.0 (15.2 in May, 15.3 in July, 15.4 in > September, 15.5 in November, 16.0 i

Re: [Twisted-Python] Deprecating subproject packaging

On 22/04/15 09:04, HawkOwl wrote: Hi, I think that Twisted should deprecate subproject packaging -- they Agreed. It's largely pointless. ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listin

Re: [Twisted-Python] Deprecating subproject packaging

> I think this is a good idea and am willing to put the work in to implement > this. Does anyone object to this? Is there a use case for keeping the > subprojects packagable that I don't know about? +10 1. The split is due to Twisted not fitting on actual diskettes in ancient times. 2. It adds