On 7 July 2016 at 00:27, Steve Dower wrote:
> I consider making stdlib modules "optional" like this to be completely
> separate from making them individually versioned - can't quite tell whether
> you guys do as well?
The point of overlap I see is that if the stdlib starts putting some
selected m
On 06Jul2016 0753, Steve Dower wrote:
Thrashing out details should go on the workflow SIG, and I guess I'm the
obvious candidate to push it asking. But given my own time constraints
right now, I'm not going to dive into details if the high level concept
(stdlib packages can be individually update
Thrashing out details should go on the workflow SIG, and I guess I'm the
obvious candidate to push it asking. But given my own time constraints right
now, I'm not going to dive into details if the high level concept (stdlib
packages can be individually updated by end users apart from a full CPyt
I consider making stdlib modules "optional" like this to be completely separate
from making them individually versioned - can't quite tell whether you guys do
as well?
To everyone: please don't conflate these two discussions. The other is about
CPython workflow and this one is about community/u
On 6 July 2016 at 14:55, Steve Dower wrote:
> I think the wsgiref issue was that it wasn't in site-packages and so
> couldn't be removed or upgraded. Having the dist-info available and putting
> them in site-packages (or a new directory?) lets us handle
> querying/replacing/removing using the exis
I think the wsgiref issue was that it wasn't in site-packages and so couldn't
be removed or upgraded. Having the dist-info available and putting them in
site-packages (or a new directory?) lets us handle querying/replacing/removing
using the existing tools we use for distribution.
Also, I think
On 6 July 2016 at 10:01, Petr Viktorin wrote:
> 4) Adjust pip to ignore installed stdlib modules that are present, so
> distributions can depend on "statistics" and not "statistics if
> python_ver<3.4". (statistics is just an example, obviously this would
> only work for modules added after the PE
On Wed, Jul 6, 2016 at 7:01 PM, Petr Viktorin wrote:
> Maybe a good short-term solution would be to make "import tkinter" raise
> ImportError("Run `dnf install tkinter` to install the tkinter module")
> if not found. This would prevent confusion while keeping the status quo.
> I'll look into that.
On 07/06/2016 05:11 AM, Steven D'Aprano wrote:
> On Tue, Jul 05, 2016 at 08:01:43PM +0200, Petr Viktorin wrote:
>
>> In the tkinter case, compiling for source is easy on a developer's
>> computer, but doing that on a headless server brings in devel files for
>> the entire graphical environment.
>>
