Fwd: Re: [ANNOUNCE] inotifyx version 0.2.0
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: Wed, 10 Aug 2011 10:13:58 -0400
From: Forest Bond
To: Ritesh Raj Sarraf
Hi Ritesh,
Looks like this is generated in pydoc.py from the standard library:
def getdocloc(self, object):
"""Return the location of module docs or None"""
try:
file = inspect.getabsfile(object)
except TypeError:
file = '(built-in)'
docloc = os.environ.get("PYTHONDOCS",
"http://docs.python.org/library";)
docdir = '/usr/share/doc/python%s/html/library' % sys.version[:3]
if not os.environ.has_key("PYTHONDOCS") and os.path.isdir(docdir):
docloc = docdir
basedir = os.path.join(sys.exec_prefix, "lib",
"python"+sys.version[0:3])
if (isinstance(object, type(os)) and
(object.__name__ in ('errno', 'exceptions', 'gc', 'imp',
'marshal', 'posix', 'signal', 'sys',
'thread', 'zipimport') or
(file.startswith(basedir) and
not file.startswith(os.path.join(basedir, 'site-packages'):
if docloc.startswith("http://";):
docloc = "%s/%s" % (docloc.rstrip("/"), object.__name__)
else:
docloc = os.path.join(docloc, object.__name__ + ".html")
else:
docloc = None
return docloc
I don't see it because I have inotifyx installed in my home directory at the
moment and that affects the return value of this function.
I think this is a bug in Debian's Python package. That function checks for the
"site-packages" directory, but it should also check for the "dist-packages"
directory since that's what Debian uses.
What do you think?
Thanks,
Forest
--
Forest Bond
http://www.alittletooquiet.net
http://www.rapidrollout.com
On Wed, Aug 10, 2011 at 07:32:25PM +0530, Ritesh Raj Sarraf wrote:
> On 08/10/2011 07:07 PM, Forest Bond wrote:
> > I am midway through inotifyx packaging and have some questions for you.
> >
> > In the previous releases, I was using epydoc to generate some docs for
> > inotifyx.py. Now that that is gone, I'm going to drop it.
> > Okay. I don't know epydoc at all, but I would think you'd still be able to
> > generate documentation with the new code organization.
> epydoc can generate documentation off of a python .py module. That was
> something I added extra. Since inotifyx.py is not shipped anymore, I'll
> just drop that from my build config.
> >> When you do a help(inotifyx), it links:
> >>
> >> MODULE DOCS
> >> http://docs.python.org/library/inotifyx
> >>
> >> for documentation. This is incorrect and we should fix this?
> > Curious, I don't see this.
> >
> > Did you download the tarball from PyPI? There was a bad tarball available
> > there
> > for a few days, which I've since removed. This was an unexpected side
> > effect of
> > publishing the code on PyPI instead of only on Launchpad. Can you check if
> > using the official release tarball fixes things?
> Nope. I downloaded the tarball from launchpad today. Built the package
> and during testing it, I noticed.
> I've attached a screenshot of the problem.
>
> --
> Ritesh Raj Sarraf
> RESEARCHUT - http://www.researchut.com
> "Necessity is the mother of invention."
signature.asc
Description: OpenPGP digital signature
can someone upload package python-captcha ?
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 326D 8438 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e43d455.3080...@irisa.fr
Re: can someone upload package python-captcha ?
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 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 326D 8438 > > > > -- > To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/4e43d455.3080...@irisa.fr > > -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capdtaj1v96jw5smkcwpyaqohqjzt2ckscpnhr9q7nszhzt9...@mail.gmail.com
Re: Python 3 BoF at DebConf11
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 >complained², no feature request for dh_python3... so I talked a little >bit about PEP 3147, PEP 3149, new and shiny PEP 402 and about status of >py3multibuild GSoC project (which already supports more build systems >than dh/cdbs, Mesutcan is working on integrating it with CDBS/dh >sequencer now). Fantastic! I really wish I could have made more progress with Python 3 porting during the current Ubuntu cycle, but the dh_python2 transition was just an enormous amount of work. We're down to the wire though - not everything converted, but we will be eliminating python-support and python-central from our CD/DVD images. Lots of patches submitted to Debian too, and I've seen many positive responses from the package maintainers. Anyway, with that task done, I do want to return to Python 3 work. I'm really glad to hear about py3multibuild progress. How can I begin to play with on my Wheezy systems now? (maybe start by reading up on it again ;). >We discussed /usr/bin/python2 symlink issue shortly and we all agreed >that we don't want Debian to use it (should helpers change shebangs back >to /usr/bin/python? Should lintian warn about it?) although we might >want to ship it with Wheezy to follow other distributions³. I definitely don't think we should do anything until and unless PEP 394 gets accepted. >/usr/bin/python will point to Python 2 in Debian for a while (Wheezy and >Wheezy+1 for sure). /usr/bin/python3 might point to python3.3 instead of >3.2, though. Python 3.3 should be released short after Wheezy freeze, >but we'll have RC releases in unstable before the freeze and it could be >possible to replace 3.2 with 3.3 in supported Python 3 versions (but >that's something we'll consider later, after checking how much work is >needed for the transition). Should we consider supporting both 3.2 and 3.3 in Wheezy? It's much easier for us to do that now. :) >The good news is that Andreas will port britney⁴ to Python 3 really soon >now (but I might misunderstood something, as usual ;-) > >Anyway, it should be a lot easier to add python3-* packages in 1-2 >months (py3build will be integrated in python3-defaults package and >dh_python3 will get some improvements). \o/ -Barry signature.asc Description: PGP signature
Re: /usr/bin/python2 again
* 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 Debian developers, and they call | their system stable! we'll get: | oh, look, there's /usr/bin/python2 and /usr/bin/python3 binaries | so it should be safe to change /usr/bin/python symlink, lets | do that, ... Damn Debian developers! a *LOT* more often (changes between 2.X versions are not that big compared to 2.X-3.X ones 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. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110811173425.ga8...@jwilk.net
Re: /usr/bin/python2 again
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 (should it be distutils or OS vender) should rewrite that to the appropriate #! line. That should include if `python2` were used there too. -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110811134249.371b9...@resist.wooz.org
