On Aug 11, 2011, at 07:34 PM, Jakub Wilk wrote:
>I'm more worried about Debian-using upstreams who'd start to
>#!/usr/bin/python2 shebangs, thus breaking compatibility with the rest of the
>world.
Then the upstream is broken. Upstream should release with
#!/usr/bin/env python
and the installer
* Piotr Ożarowski , 2011-08-10, 15:03:
Why not make Python 2 point to /usr/bin/python2?
because instead of:
| oh, look, /usr/bin/python is a symlink, lets use different 2.X version,
| I don't care about 2.Y anymore and I want 2.Z by default. What? foo
| application doesn't work anymore? Damn De
Thanks for the update Piotr! I wish I could have made it, but it conflicted
with family vacations.
On Aug 08, 2011, at 11:50 PM, Piotr Ożarowski wrote:
>At DebConf11 in Banja Luka, we had a short discussion¹ about Python 3
>support in Debian. Apparently everything is very good, nobody
>complaine
Olivier, patience is a virtue. There's no need to send a follow-up
email every other day. The usual "timeout" is two week without reply,
then send another email.
On Thu, Aug 11, 2011 at 15:08, Olivier Sallou wrote:
> Hi,
> package python-captcha (named python-pycaptcha on svn) needs to be uploade
Hi,
package python-captcha (named python-pycaptcha on svn) needs to be uploaded.
I have fixed most lintian warnings and tested the package.
Can a DD take it in its TODO list?
Thanks
Olivier
--
gpg key id: 4096R/326D8438 (pgp.mit.edu)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB
Hello Python Team,
Is this problem Debian specific? The package is installing its modules
under /usr/lib/python2.6/dist-packages, which as Forest mentions, is not
handled by pydoc currently.
Ritesh
Original Message
Subject:Re: [ANNOUNCE] inotifyx version 0.2.0
Date: W
6 matches
Mail list logo
