Hi everyone,
As many know, one of the things that makes the Twisted project so unique is our conformance to our Compatibility Policy. This policy means that users of Twisted can freely upgrade between versions with all incompatibilities being warned about before causing code to break. However, for a while, one part of the compatibility policy has caused issues - what we do with code that has been deprecated for a long time, and at least the release + 2 & 1 year after.
The existing policy states:
"Removal should happen once the deprecated API becomes an additional maintenance burden. For example, if it makes implementation of a new feature more difficult, if it makes documentation of non-deprecated APIs more confusing, or if its unit tests become an undue burden on the continuous integration system. Removal should not be undertaken just to follow a timeline."
This makes the only reasonable cause for any code being removed from Twisted is if it is a maintenance burden, but does not take into account the effect that keeping large amounts of deprecated code has on new, existing, and future Twisted users. It does specify that it should be removed if it makes documentation of non-deprecated APIs confusing, but by its very existence, it makes what should be "best practice" more confusing -- especially if the deprecated API is "simpler" at first glance, but was deprecated because of vast underlying issues,
Discussions have come to the conclusion that the exact reverse of this policy should be instated:
"Removal of code should occur as soon as the deprecation grace period has ended."
The reason for this is that a leaner Twisted is a better Twisted -- we should strive to not break existing applications, but we have the deprecation policy in place to ensure that breakage is, if all goes to plan, never out of the blue. Less code surface means that Twisted is easier to learn for new users and Twisted-using projects onboarding new people, easier to use for established users with a clear best practice, and easier to maintain because the codebase is not a web of things we deprecated and then never removed. We believe this change benefits everyone.
This is also similar to the deprecation policy of another time-based releasing project, Django (https://docs.djangoproject.com/en/1.8/internals/release-process/#internal-r…), where releases are every 9 months and code is *always* removed in Release where deprecated + 2, giving them a deprecation grace period of up to 1 and a half years.
If you have any opinions on this change, please let me know, and we'll take it all into account before changing the policy.
Twisted Regards,
Amber "Hawkie" Brown
Twisted Release Manager
9位QQ出售地址：http://yz.hzhack.com/?post=88位QQ出售地址：http://yz.hzhack.com/?post=7
看中的老板，请抖我。保证高安全卖号！要的给我联系：2500994985
------------------ Original ------------------
From: "twisted-web-request";<twisted-web-request(a)twistedmatrix.com>;
Date: Wed, Oct 14, 2015 02:00 AM
To: "twisted-web"<twisted-web(a)twistedmatrix.com>;
Subject: Twisted-web Digest, Vol 128, Issue 1
Send Twisted-web mailing list submissions to
twisted-web(a)twistedmatrix.com
To subscribe or unsubscribe via the World Wide Web, visit
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
or, via email, send a message with subject or body 'help' to
twisted-web-request(a)twistedmatrix.com
You can reach the person managing the list at
twisted-web-owner(a)twistedmatrix.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Twisted-web digest..."
Today's Topics:
1. Changes to Twisted's binary distribution (Amber "Hawkie" Brown)
----------------------------------------------------------------------
Message: 1
Date: Tue, 13 Oct 2015 09:33:42 +0800
From: "Amber \"Hawkie\" Brown" <hawkowl(a)atleastfornow.net>
To: twisted-web(a)twistedmatrix.com, Twisted-Python
<twisted-python(a)twistedmatrix.com>
Subject: [Twisted-web] Changes to Twisted's binary distribution
Message-ID: <4DF8DEC8-6EA9-4EE6-9808-D98C11088DE2(a)atleastfornow.net>
Content-Type: text/plain; charset="us-ascii"
Hi everyone,
Just letting everyone know, the next release (Twisted 15.5) will not include MSI or EXE installers for Windows, only binary wheels, and installation through pip or from source dist will be the only supported method of installation. The exe/msi installers didn't work well (or at all?) for virtualenvs, and when we (eventually) start shipping binary wheels for OS X, it'll make everything more consistent.
Regards,
Amber "Hawkie" Brown
Twisted Release manager
GPG: https://keybase.io/hawkowl
hawkowl(a)atleastfornow.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://twistedmatrix.com/pipermail/twisted-web/attachments/20151013/7c54c93…>
------------------------------
_______________________________________________
Twisted-web mailing list
Twisted-web(a)twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
End of Twisted-web Digest, Vol 128, Issue 1
*******************************************
Hi everyone,
Just letting everyone know, the next release (Twisted 15.5) will not include MSI or EXE installers for Windows, only binary wheels, and installation through pip or from source dist will be the only supported method of installation. The exe/msi installers didn't work well (or at all?) for virtualenvs, and when we (eventually) start shipping binary wheels for OS X, it'll make everything more consistent.
Regards,
Amber "Hawkie" Brown
Twisted Release manager
GPG: https://keybase.io/hawkowl
hawkowl(a)atleastfornow.net
