+1 (and yay!)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
___
Python-Dev mailing list
Python
[Toshio Kuratomi, 2011-03-03]
> On Thu, Mar 03, 2011 at 09:55:25AM +0100, Piotr Ożarowski wrote:
> > If /usr/bin/python will be disallowed in shebangs on the other hand
> > (and all scripts will use /usr/bin/python2, /usr/bin/python3,
> > /usr/bin/python4 or /usr/bin/python2.
[Guido van Rossum, 2011-03-02]
> On Wed, Mar 2, 2011 at 4:56 AM, Piotr Ożarowski wrote:
> > [Sandro Tosi, 2011-03-02]
> >> On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski wrote:
> >> > I co-maintain with Matthias a package that provides /usr/bin/python
> >>
;-)
* how many Python packages do Arch have in the first place and why so
little? ;-)
* how does Arch deal with scripts that are not packaged, what do you say
to users who report bugs against your packages because their local
scripts do not work anymore? :-|
--
Piotr
it require to fix every single one
of them to point to /usr/bin/python2 instead? Even if we'd start checking
mdate and change it at build time automatically, there still will be way
too many false positives... for no clear gain.
--
Piotr Ożarowski Debian GNU/Linux Dev
[Sandro Tosi, 2011-03-02]
> On Wed, Mar 2, 2011 at 13:56, Piotr Ożarowski wrote:
> > [Sandro Tosi, 2011-03-02]
> >> On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski wrote:
> >> > I co-maintain with Matthias a package that provides /usr/bin/python
> >> > s
[Sandro Tosi, 2011-03-02]
> On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski wrote:
> > I co-maintain with Matthias a package that provides /usr/bin/python
> > symlink in Debian and I can confirm that it will always point to Python
> > 2.X. We also do not plan to add /usr/bin/p
t to Python
2.X. We also do not plan to add /usr/bin/python2 symlink (and I guess
only accepted PEP can change that)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A
I'm not sure what we'll do with it (we still have to
figure out what to do with modules that work with 3.2 only and cannot be
patched due to f.e. from __future__ imports)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozar
, as there are many modules with
things like:
os.path.join(os.path.dirname(__file__), '..', '..', '..', '..', 'share',
'foo')
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
*one* place and later import the result in other parts of
the code (instead of using __file__ again)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7
em,
* release a new version without testing it with your own unit tests first
to ensure that it will fail when your favourite Debian Developer tries
to build it
;-)
[debian-pyt...@l.d.o BCCed]
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl
12 matches
Mail list logo