Re: Python Policy: Things to consider for Stretch

To: debian-python@lists.debian.org
Subject: Re: Python Policy: Things to consider for Stretch
From: Scott Kitterman <debian@kitterman.com>
Date: Fri, 29 Jan 2016 17:20:07 -0500
Message-id: <[🔎] 1981644.1AZ1zIRFG5@kitterma-e6430>
In-reply-to: <[🔎] 854me0ki50.fsf@benfinney.id.au>
References: <[🔎] 1705132.RfqMtW1P2v@kitterma-e6430> <[🔎] 85r3h7k0cc.fsf@benfinney.id.au> <[🔎] 854me0ki50.fsf@benfinney.id.au>

On Tuesday, January 26, 2016 04:46:19 PM Ben Finney wrote:
...
>   Once these non-semantic changes are accepted I will begin work on the
>   second stage of semantic changes.
...

OK.  Those are all accepted.  Barry Warsaw had done some changes in the -whl 
section so I made an attempt at merging what the two of you had done.

Thanks,

Scott K

Reply to:

Follow-Ups:
- Re: Python Policy: Things to consider for Stretch
  - From: Ben Finney <ben+debian@benfinney.id.au>

References:
- Python Policy: Things to consider for Stretch
  - From: Scott Kitterman <debian@kitterman.com>
- Re: Python Policy: Things to consider for Stretch
  - From: Ben Finney <ben+debian@benfinney.id.au>
- Re: Python Policy: Things to consider for Stretch
  - From: Ben Finney <ben+debian@benfinney.id.au>

Prev by Date: Bug#813147: ITP: emcee -- Kick ass affine-invariant ensemble MCMC sampling for Python
Next by Date: Re: New, updated pip coming
Previous by thread: Re: Python Policy: Things to consider for Stretch
Next by thread: Re: Python Policy: Things to consider for Stretch
Index(es):
- Date
- Thread