Re: Question about private modules in /usr/share

2015-04-21 Thread Potter, Tim (Cloud Services)
On 21 Apr 2015, at 7:01 pm, Piotr Ożarowski wrote: > > [Potter, Tim (Cloud Services), 2015-04-21] >> binary gives an import error since /usr/share/dwarf isn’t in the PYTHONPATH: >> >> # dwarf >> Traceback (most recent call last): >> File "/usr/bin/dwarf", line 32, in >>from dwarf import lo

Re: [Python-modules-team] Bug#782756: should not be in Section: python

2015-04-21 Thread Brian May
On Tue, 21 Apr 2015 at 14:38 Damyan Ivanov wrote: > Its description says "static site generator". Sounds a lot like HTTP > to me, not less than ikiwiki for example. > I think you might be getting HTTP confused with HTML. Both ikiwiki and mkdocs turn files into static HTML files, but neither sup

Re: /usr/bin/python in Python 2 and 3

2015-04-21 Thread Dimitri John Ledkov
#!/usr/bin/python32 For bilingual scripts. On 17 Apr 2015 2:30 pm, "Geoffrey Thomas" wrote: > I've written up the proposal I made a few days ago for a /usr/bin/python > launcher that keeps the API of being Python 2, but lets scripts opt in to > running on Python 3: > > https://ldpreload.com/blog

Re: /usr/bin/python in Python 2 and 3

2015-04-21 Thread Thomas Kluyver
On 21 April 2015 at 08:15, Barry Warsaw wrote: > >For third parties who want to distribute scripts that run out-of-the-box > >everywhere (installers, cross-platform system management or monitoring > >scripts, build scripts, etc.), Python 3 isn't an option. If we remove > Python > >2 from the defa

Re: /usr/bin/python in Python 2 and 3

2015-04-21 Thread Barry Warsaw
On Apr 21, 2015, at 10:42 AM, Geoffrey Thomas wrote: >For third parties who want to distribute scripts that run out-of-the-box >everywhere (installers, cross-platform system management or monitoring >scripts, build scripts, etc.), Python 3 isn't an option. If we remove Python >2 from the default i

Re: /usr/bin/python in Python 2 and 3

2015-04-21 Thread Geoffrey Thomas
On Tue, 21 Apr 2015, Dmitry Shachnev wrote: To be honest, I don't like this proposal. - Newly written code should *just* use Python 3 (there are exceptions, but very few). - If existing code supports Python 3, and its developers consider Python 3 as a target platform, then it should *just* u

Re: /usr/bin/python in Python 2 and 3

2015-04-21 Thread Dmitry Shachnev
Hi, On Fri, 17 Apr 2015 17:11:45 -0400 (EDT), Geoffrey Thomas wrote: > I've written up the proposal I made a few days ago for a /usr/bin/python > launcher that keeps the API of being Python 2, but lets scripts opt in to > running on Python 3: > > https://ldpreload.com/blog/usr-bin-python-23 > > Le

Re: Question about private modules in /usr/share

2015-04-21 Thread Piotr Ożarowski
[Potter, Tim (Cloud Services), 2015-04-21] > binary gives an import error since /usr/share/dwarf isn’t in the PYTHONPATH: > > # dwarf > Traceback (most recent call last): > File "/usr/bin/dwarf", line 32, in > from dwarf import log # pylint: disable=W0611 > ImportError: No module named dw