increasing the python requirement

Toshio Kuratomi a.badger at gmail.com
Tue Jan 4 22:53:19 UTC 2011


On Tue, Jan 04, 2011 at 03:56:42PM -0600, John Arbash Meinel wrote:
> >> Even if we have to do such focused backports, I think the corresponding
> >> effort is still worth the benefits of having to support only 2 different
> >> versions of python instead of 4.
> 
> One thing to consider, is if there is a new repo format, to provide it
> as a plugin to bzr <=2.3.
> 
> >>
> > If you do backports of new formats to the version of bzr that supports
> > python-2.4 that strikes a great balance as far as I'm concerned.
> > 
> > I still have to keep bzr running on RHEL5 for people who use it there until
> > RHEL5 EOLs and the big thing is *not* performance optimizations, new
> > software that targets new APIs, and such... end users understand that those
> > types of things may require a newer version of python/bzr.  It really is just --
> > "I'm running RHEL5 and I need to interoperate with the repository format on
> > launchpad to checkout the latest version of gwibber" or "I'm running bzr
> > smart server on a RHEL5 server and a few of the clients pushing repos get
> > errors because they default to the new format."
> > 
> > -Toshio
> 
> There are no immediate plans to implement a new format. But it is
> certainly something that we would be unlikely to backport into an old
> stable release.
> 
A plugin would be fine (as long as it works ;-).  Is that what you're
proposing?

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110104/039258dd/attachment.pgp>


More information about the bazaar mailing list