[Bug 716789] Re: dh_pysupport fails to move zero-byte __init__.py
This package has been deleted from Ubuntu, starting from Xenial. ** Changed in: python-support (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716789 Title: dh_pysupport fails to move zero-byte __init__.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-support/+bug/716789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716789] Re: dh_pysupport fails to move zero-byte __init__.py
Please don't take this bug report personally. My intent here is merely to document the problem. Writing a patch comes later. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716789 Title: dh_pysupport fails to move zero-byte __init__.py -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 716789] Re: dh_pysupport fails to move zero-byte __init__.py
[Forest, 2011-02-11] > I think you're missing my point. I don't want to force python-support > to generate an __init__.py file at all. I want it (and dh_pysupport) to > use my original one. Always. Not just when my file is a certain number > of bytes. nobody is forcing you to use dh_pysupport, feel free to use one of two other helper tools or take care of byte compilation yourself or send a patch that will deal with Python namespace mess better than dh_pysupport does. EOT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716789 Title: dh_pysupport fails to move zero-byte __init__.py -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716789] Re: dh_pysupport fails to move zero-byte __init__.py
Hi, Piotr. I think you're missing my point. I don't want to force python-support to generate an __init__.py file at all. I want it (and dh_pysupport) to use my original one. Always. Not just when my file is a certain number of bytes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716789 Title: dh_pysupport fails to move zero-byte __init__.py -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 716789] Re: dh_pysupport fails to move zero-byte __init__.py
[Forest, 2011-02-11] > Okay, I read the README. It basically says three things regarding this > issue: python-supports regenerates empty __init__.py files via dpkg trigger, once all packages are installed. If you want to force it to regenerate it sooner, just invoke update-python-modules in postinst or use dh_python2 instead. let me quote the relevant part for you again: | What this means is, if you need a namespace package or depend on a | package that needs it, *and* that you need to use it during the | postinst phase (e.g. for a daemon), you will have to add the following | command in the postinst before starting your daemon: | update-python-modules -p -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716789 Title: dh_pysupport fails to move zero-byte __init__.py -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716789] Re: dh_pysupport fails to move zero-byte __init__.py
Okay, I read the README. It basically says three things regarding this issue: 1. That some python "modules" rely on the absence of __init__.py in some directories, and that those python packages are broken. That may be true, but my package is not one of them. It has its own __init__.py, placed exactly where it should be. 2. That python-support will create empty __init__.py files as needed, after postinst. I guess that might be a handy feature for the aforementioned broken python packages, but my python package is not one of them. It has its own __init__.py, placed exactly where it should be. Having python- support ignore it and create a new one later only serves to create confusing and broken behavior. Having python-support behave this way only sometimes (when the file happens to be zero bytes) makes it even more confusing and arguably even more broken. 3. That a postinst script can coerce python-support to create __init__.py earlier by calling update-python-modules -p before starting a python daemon. Again, I don't want python-support creating __init__.py for me at all. My python package already has one. I want python-support to simply respect the one that is already there, copy it into the correct place when dh_pysupport runs, and let it be unpacked when the deb package is installed. This is (thankfully) what it does when my __init__.py contains at least one byte. I expect it to do the same when it contains zero bytes. Side Note 1: The deb maintainer doesn't write the postinst code that starts the daemon. That code is added automatically by debhelper, as is the update-python-modules call, so expecting the deb maintainer to insert a special command line option and arrange the sequence events a certain way is a bit less than helpful. Side Note 2: The README claims that "namespace packages are empty __init__.py files." I'm not sure where the author got that idea, but it's not correct. I suppose some namespace packages may contain an empty __init__.py, but other python packages contain them as well, and a namespace package is not simply an __init__.py file. http://docs.python.org/tutorial/modules.html#packages http://www.python.org/dev/peps/pep-0382/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716789 Title: dh_pysupport fails to move zero-byte __init__.py -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 716789] Re: dh_pysupport fails to move zero-byte __init__.py
please read /usr/share/doc/python-support/README.gz and then close this bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716789 Title: dh_pysupport fails to move zero-byte __init__.py -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716789] Re: dh_pysupport fails to move zero-byte __init__.py
** Summary changed: - dh_pysupport fails to move 0-byte __init__.py + dh_pysupport fails to move zero-byte __init__.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716789 Title: dh_pysupport fails to move zero-byte __init__.py -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
