[Python-Dev] IronPython 2.7.5 Released
On behalf of the IronPython team, I'm very happy to announce the release of IronPython 2.7.5[1]. Like all IronPython 2.7-series releases, .NET 4 is required to install it. Installing this release will replace any existing IronPython 2.7-series installation. Assemblies for embedding are provided for .NET 3.5, .NET 4, .NET 4.5, and Silverlight 5. IronPython 2.7.5 is primarily a collection of bug fixes[2] which smooths off many of the remaining rough edges. The complete list of changes[3] is also available. A major new feature is the inclusion of `ensurepip`, which will install the `pip` package manager: ``` ; -X:Frames is required when using pip ipy.exe -X:Frames -m ensurepip ; Run from an Administrator console if using IronPython installer ipy.exe -X:Frames -m pip install html5lib ``` **Note:** The assembly version of IronPython has changed to 2.7.5.0. All previous 2.7 versions had the same version (2.7.0.40) which caused issues when different versions were installed. Publisher policy files are used to so that applications don't have to be recompiled, but recompiling is strongly recommended. A huge thanks goes out to Pawel Jasinski, who contributed most of the changes in this release. Thanks is also due to Simon Opelt, Alex Earl, Jeffrey Bester, yngipy hernan, Alexander Köplinger,Vincent Ducros, and fdanny. For Visual Studio integration, check out Python Tools for Visual Studio[4] which has support for IronPython as well as CPython, and many other fantastic features. IronPython 2.7.5 is also available for embedding via NuGet. The main package is IronPython, and the standard library is in IronPython.StdLib. - Jeff [1] http://ironpython.codeplex.com/releases/view/169382 [2] http://bit.ly/ipy275fixed [3] https://github.com/IronLanguages/main/compare/ipy-2.7.4...ipy-2.7.5 [4] http://pytools.codeplex.com/ ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Making it possible to accept contributions without CLA (was: My thinking about the development process)
On 9 Dec 2014 08:47, "Barry Warsaw" wrote: > > On Dec 09, 2014, at 09:31 AM, Ben Finney wrote: > > >Rather, I'm asking what, specifically, necessitates this situation. > > > >What would need to change, for the PSF to accept contributions to the > >Python copyrighted works, without requiring the contributor to do > >anything but license the work under Apache 2.0 license? > > My understanding is that the PSF needs the ability to relicense the > contribution under the standard PSF license, and it is the contributor > agreement that gives the PSF the legal right to do this. This matches my understanding as well. The problem is that the PSF licence itself isn't suitable as "licence in", and changing the "licence out" could have a broad ripple effect on downstream consumers (especially since the early history means "just change the outgoing license to the Apache License" isn't an available option, at least as far as I am aware). A more restricted CLA that limited the PSF's outgoing licence choices to OSI approved open source licenses might address some of the concerns without causing problems elsewhere, but the combination of being both interested in core development and having a philosophical or personal objection to signing the CLA seems to be genuinely rare. Cheers, Nick. > > Many organizations, both for- and non-profit have this legal requirement, and > there are many avenues for satisfying these needs, mostly based on different > legal and business interpretations. In the scheme of such things, and IMHO, > the PSF CLA is quite reasonable and lightweight, both in what it requires a > contributor to provide, and in the value, rights, and guarantees it extends to > the contributor. > > Cheers, > -Barry > ___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Making it possible to accept contributions without CLA (was: My thinking about the development process)
On Dec 09, 2014, at 07:42 PM, Nick Coghlan wrote: >A more restricted CLA that limited the PSF's outgoing licence choices to >OSI approved open source licenses might address some of the concerns >without causing problems elsewhere, but the combination of being both >interested in core development and having a philosophical or personal >objection to signing the CLA seems to be genuinely rare. The CLA does explicitly say "Contributor understands and agrees that PSF shall have the irrevocable and perpetual right to make and distribute copies of any Contribution, as well as to create and distribute collective works and derivative works of any Contribution, under the Initial License or under any other open source license approved by a unanimous vote of the PSF board." So while not explicitly limited to an OSI approved license, it must still be "open source", at least in the view of the entire (unanimous) PSF board. "OSI approved" would probably be the least controversial definition of "open source" that the PSF could adopt. Cheers, -Barry pgp7O9fxtjjZZ.pgp Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
