On Wed, Jan 21, 2015 at 08:15:59AM -0500, Andrew Schulman wrote:
> > > After much deliberation, I have decide to put my packages up for
> > > adoption. I have not had enough free time to properly maintain my
> > > packages for quite some time. Unfortunately, this is not going to
> > > change for th
> > After much deliberation, I have decide to put my packages up for
> > adoption. I have not had enough free time to properly maintain my
> > packages for quite some time. Unfortunately, this is not going to
> > change for the foreseeable future.
>
> No worries, hopefully you're busy with good th
On Jan 21 00:54, Yaakov Selkowitz wrote:
> On Tue, 2015-01-20 at 20:50 -0500, Jason Tishler wrote:
> > On Wed, Jan 14, 2015 at 02:03:34AM -0600, Yaakov Selkowitz wrote:
> > > Python 3.2 is no longer supported upstream, and many packages now
> > > require newer versions. Any idea on a timeframe for
On Tue, 2015-01-20 at 20:50 -0500, Jason Tishler wrote:
> On Wed, Jan 14, 2015 at 02:03:34AM -0600, Yaakov Selkowitz wrote:
> > Python 3.2 is no longer supported upstream, and many packages now
> > require newer versions. Any idea on a timeframe for a coordinated
> > upgrade to 3.4.2?
>
> After m
On Wed, Jan 14, 2015 at 02:03:34AM -0600, Yaakov Selkowitz wrote:
> Python 3.2 is no longer supported upstream, and many packages now
> require newer versions. Any idea on a timeframe for a coordinated
> upgrade to 3.4.2?
After much deliberation, I have decide to put my packages up for
adoption.
Jason,
Python 3.2 is no longer supported upstream, and many packages now
require newer versions. Any idea on a timeframe for a coordinated
upgrade to 3.4.2?
Yaakov
