Re: python MySQLdb no longer works
On Tue, 2006-08-22 at 16:14 -0400, Rick Pasotto wrote: > I update to 'testing' daily. Suddenly I can no longer connect to mysql > using python. This is the error traceback: > > What happened? How can I fix it? http://bugs.debian.org/383603 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: joining the python modules packaging team
On 4/5/07, Michel Casabona <[EMAIL PROTECTED]> wrote: I'd like to join the team to maintain the python-hachoir packages that I build, which will be soon uploaded to debian (thanks a lot to Piotr Ożarowski), and help maintaining other packages if possible. Thanks heaps for that, hachoir sounds really cool and very useful for folks doing reverse engineering and other related things. -- bye, pabs http://wiki.debian.org/PaulWise
Re: Debian 4.1 and Python 2.5
On Thu, Feb 14, 2008 at 7:49 PM, David Paleino <[EMAIL PROTECTED]> wrote: > Those page I linked states that python2.5 is already in testing, not that it > will be the "default". I believe this should be asked on > [EMAIL PROTECTED] [1]: feel free to send a mail there and ask them > to keep you CCed. Please see this thread and these bugs: http://lists.debian.org/debian-release/2008/01/msg00213.html http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python2.5;[EMAIL PROTECTED] -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Python related changes for unstable/squeeze
On Tue, Feb 17, 2009 at 6:03 AM, Piotr Ożarowski wrote: > [Matthias Klose, 2009-02-16] >> Besides the "normal" pending update of the python version for the >> unstable distribution, there will be more changes around python >> packaging, including the introduction of python-3.x and addressing >> some packaging issues. How do other distributions deal with these issues? Will the need for special per-tool directories ever be obsoleted by upstream? -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bzr lightweight checkout, bzr shallow branches, and git
On Tue, Mar 3, 2009 at 1:37 AM, Adeodato Simó wrote: > 3. Git > == > > Git has shallow clones, created with the --depth option for git-clone. > This cut-offs the history of the project past a certain point, but the > result is lacking: mainly, you cannot push your changes back. (You can > do local commits however, and you can create patches for this in the > normal Git workflow.) This is wrong, you most certainly *can* push from a shallow clone to a full clone. I think you cannot (yet) push to a shallow clone though (haven't tried it myself). -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bzr lightweight checkout, bzr shallow branches, and git
On Tue, Mar 3, 2009 at 8:04 PM, Adeodato Simó wrote: > A shallow repository has a number of limitations (you cannot clone > or fetch from it, nor push from nor into it) [...] > ^ > > Can you confirm whether my reading of the underlined part was correct in > assuming it meant you couldn't push from a shallow clone to a full clone? It appears you reading is correct. I thought the docs said something else, although I'm clearly mistaken. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Backporting to Etch
On Fri, May 15, 2009 at 7:18 PM, Andrew Malcolmson wrote:
> This runs and informs me that the following dependencies are missing:
> tk8.5-dev, libffi-dev (>= 3.0.5), libgpm2, python-sphinx
>
> How do I tell pbuilder that I don't need these features?
>From the source directory, run dch --bpo and edit debian/control and
remove the appropriate build-depends. Then rebuild the source package
and rebuild the package.
> Is there a better way to do a backport? I could manually compile the
> source in an Etch chroot but I still wouldn't know which configure
> options are needed to disable the above features ('configure --help'
> doesn't show them)
No idea about that.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: License entry in egg info files
On Sat, Oct 17, 2009 at 9:50 PM, Ben Finney wrote: > I disagree. This issue in the ‘setup.py’ settings is upstream's > responsibility. Lintian is best reserved for reporting problems that are > the Debian package maintainer's responsibility. Do you object to spelling-error-in-binary, duplicated-key-in-desktop-entry, embedded-zlib, duplicate-font-file or the other lintian tests that check upstream stuff? Also, it is the maintainer's responsibility to point out upstream problems to upstream, if lintian can help automatically detect such problems, I think it is a good idea to do so. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: License entry in egg info files
On Sun, Oct 18, 2009 at 6:46 AM, Ben Finney wrote: > Paul Wise writes: > >> Do you object to spelling-error-in-binary, >> duplicated-key-in-desktop-entry, embedded-zlib, duplicate-font-file or >> the other lintian tests that check upstream stuff? > > I think they lead to widely-used, persistent overrides, and I think such > overrides are an indicator that the specific check is inappropriate. Sounds like you have observed people using overrides inappropriately. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552001: RFP: pyquery -- A jQuery-like library for python
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-python@lists.debian.org * Package name: pyquery Version : 0.3 Upstream Author : Olivier Lauzanne * URL : http://pyquery.org/ * License : BSD Programming Lang: Python Description : A jQuery-like library for python -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: pymol vs numpy conflict
On Wed, Nov 11, 2009 at 8:08 AM, Jeremiah H. Savage wrote: > However, a problem arises when I attempt to use pymol in the same > program. First, to use the pymol api, I add the following to > ~/.bashrc: > > PYMOL_PATH=/usr/lib/pymodules/python2.5/pymol > export PYMOL_PATH > PYTHONPATH=$PYMOL_PATH > export PYTHONPATH I'd suggest not putting the pymol directory in the PYTHONPATH and instead do 'import pymol.parser' or similar. Also check how numpy is importing numpy.parser. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Advice: how to effectively maintain pyparted in Debian?
On Fri, Dec 18, 2009 at 6:31 AM, Luca Falavigna wrote: > Recently, upstream declared that pyparted is bound to Fedora libparted, > and not with upstream [3], so I'm not sure future versions will be ever > supported by our libparted. Is the issue just that upstream has not yet released a new version and Fedora has a habit of shipping vcs snapshots and pre-releases? It appears the new functions have been added upstream (search for commits by Hans de Goede): http://www.gnu.org/software/parted/download.shtml http://git.debian.org/?p=parted/parted.git;a=shortlog > How to proceed from here? Here are some scenarios: > 1. Keep things as they are now: stick with 2.2 for Squeeze, and see > what happens libbparted side in Squeeze + 1. > 2. Package 2.4, patch it to be compatible with our libparted, and face > RC bugs that will eventually be reported, without upstream support. > 3. Remove pyparted from Sid and Squeeze. None of these seem very good ideas to me, I'd suggest: Talk to upstream, Debian and Fedora maintainers for libparted, pyparted and get the forks merged and a new upstream release made so that everything is compatible. Also suggest that they release early, release often so that distros are not tempted to apply to many extra patches. If that fails, get the Fedora folks rename their forks libparted-fedora and pyparted-fedora. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: jQuery dependency for Trac 0.11 should be < 1.3
On Sat, Dec 26, 2009 at 7:06 AM, anatoly techtonik wrote: > Trac 0.11 ships with jQuery 1.2.6 > However, Debian patches remove this file in favor of libjs-jquery > package which contains version 1.3.x > This breaks plugins for Trac 0.11 that rely on 1.2.x jQuery features > removed in 1.3.x > > How to properly add dependency for jQuery<1.3 to trac package? jquery 1.2 is only available in lenny, so depending on jQuery<1.3 would make trac not installable in sid/squeeze (and thus an RC bug). Talk to Trac upstream about removing the jQuery embedded code copy, getting the plugins upgraded to jQuery 1.3 and making a new release. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: jQuery dependency for Trac 0.11 should be < 1.3
On Sat, Dec 26, 2009 at 7:23 PM, anatoly techtonik wrote: > Upstream Trac is shipped with jQuery it needs while leaving Genshi and > other libraries as dependencies. Debian specific patch removes jQuery > from Trac distribution even though it contributes only 2% to package > size. This dependency injection creates aforementioned problems. The dependency exists whether or not trac has "Depends: libjs-jquery". Removing the "Depends: libjs-jquery" sounds like the equivalent of shipping a copy of GTK+ with gnome-terminal. Or a copy of ncurses with top. Or a copy of glibc with ls or cp. None of those things are nessecary, so why should shipping a copy of jQuery with one of the packages that use it be any different? In any case I don't think the security team would appreciate reopening one of the issues from their embedded-code-copies list: http://svn.debian.org/wsvn/secure-testing/data/embedded-code-copies It is already huge and scary enough as it is. I have a feeling it is probably quite incomplete too. > There was a complex issue with TracDeveloperPlugin, which solution > involved permissions, aliases and mod_wsgi configuration. The jQuery > was only a part of a problem and it was not only downgrading that > fixed it. > > There are more than 200 plugins tagged for 0.11 on > http://trac-hacks.org/ They were developed and debugged with jQuery > 1.2.x which is not forward compatible with 1.3.x I don't feel like I > want to check if they are compatible next time I'd like to use one. > 15kBytes doesn't worth wasted hours. It sounds like you're installing the trac plugins manually rather from Debian packages. I'd suggest manually installing jquery 1.2 for the manually installed plugins that need it and putting the javascript file at a different URL to the Debian jQuery 1.3 version. If there are any trac plugins in Debian sid/squeeze that need jQuery 1.2, I'd suggest filing RC bugs. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: openshot
On Thu, Jan 21, 2010 at 11:49 AM, Jonathan Thomas wrote: > I am looking for a sponsor for my package "openshot". I reviewed this package recently and concluded that it needs work: http://lists.debian.org/debian-mentors/2010/01/msg00254.html -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Would like a sponsor to upload the new version of python-foolscap
On Fri, Jan 29, 2010 at 10:08 AM, Ben Finney wrote: > I would think a separate task tracker would be more appropriate; the > channel topic should remain primarily descriptive of the topic of the > channel, after all. I'd strongly suggest the use of PET (package entropy tracker) written by the Perl team: http://pet.alioth.debian.org/ -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: python2.6 vs python-json
So basically, Python upstream hijacked a part of the import namespace. Unless they can be convinced to undo that, python-json is clearly at a disadvantage and future JSON consuming Python code will likely use the Python json module since it comes with Python. Therefore python-json needs to be removed or renamed and the reverse dependencies need to adapt accordingly. The python-json upstream should be contacted to find out future plans for it, to decide if removal or renaming is better. The upstreams for the reverse deps probably will want to stay compatible with Python 2.5, therefore they need to be checking for the new Python API vs the old python-json API vs the possible new name for the python-json API and adapt accordingly. On Sun, Feb 14, 2010 at 7:25 AM, Jakub Wilk wrote: > - conduit contains a (slightly forked?) embedded copy of python-facebook. > However, it's a bit more clever with importing, so it'll never use > python-json (despite recommending "python (>= 2.6) | python-json"). Please report this embedded code copy to the security team for addition to embedded-code-copies: http://svn.debian.org/wsvn/secure-testing/data/embedded-code-copies -- bye, pabs http://wiki.debian.org/PaulWise -- 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/e13a36b31002131718h44b126esfc8bc13b9eff9...@mail.gmail.com
Re: RFS: pyrit
On Thu, May 20, 2010 at 9:24 PM, Christian Kastner wrote: > Pyrit is an excellent example of a GPGPU-driven application. It consists > of a main program and optional extensions for various GPGPU > technologies, such as NVIDIA CUDA and OpenCL. Do we have OpenCL support in Debian main? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktimwim0l85ovv52qhoc4oselfc6-6bxdydtjz...@mail.gmail.com
Re: RFS: pyrit
On Thu, May 20, 2010 at 10:32 PM, Christian Kastner wrote: > On 05/20/2010 03:58 PM, Paul Wise wrote: >> Do we have OpenCL support in Debian main? > > Not yet, but it's being worked on. I've been in contact with the NVIDIA > Team, they expect the NVIDIA toolkit (with CUDA and OpenCL support) to > be available RSN, see #581184. Unfortunately that is non-free. Unless pyrit works with nouveau or any of the drivers in Debian main, I think pyrit should go to contrib. > I don't anticipate an OpenCL extension for pyrit, though. That would > require binary packages for each specific vendor implementation (eg > pyrit-opencl-nvidia). You might as well just use pyrit-cuda. Err, isn't the whole point of OpenCL that it is cross-vendor??? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktimecb4ovxt2-0w5jd2boarurh1z1efdu5zt9...@mail.gmail.com
Re: Policy for "Specifying Supported Versions" for Python3
On Tue, Jun 22, 2010 at 6:30 AM, Scott Kitterman wrote: > If we maintain a standard that if in Python you import foo, then the Python > package name is python-foo and the Python3 package is names python3-foo, I > would think this is manageable. I think that adding this metapackage would > impose a lot of complexity on packagers and/or python helper maintainers, > bloat the Packages.gz file signficantly, and probably provide confusing search > results. What is the point of separate python-foo/python2-foo and python3-foo packages? Will they be separate source packages or just binary packages? Will we rename the python3-foo packages to python-foo once python 2 is gone? After python 2 is gone will we add new packages named python-foo and have old python3-bar packages in the archive at the same time? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktimxhu2rsiy9wz4y-n8phj4ktu5cf6zuvhy5k...@mail.gmail.com
Re: Policy for "Specifying Supported Versions" for Python3
I don't agree with your analysis. I was hoping someone else would speak up before your proposal got implemented, but I can see that doesn't look like it will happen. I would like you to consult with a wider audience, at least -devel and -release, before Debian changes the python policy yet again. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktik1sig1jhqbodjo3mmisqfvx6prrn8ww-26o...@mail.gmail.com
Re: Proposed Email to the release team about XS/B-P-V
On Thu, Jun 24, 2010 at 1:15 AM, Scott Kitterman wrote: > In Debian Python we are currently discussing how best to specify version > information for Python 3. There is a strong (but not unanimous) view among > the participants in debian-pyt...@l.d.o and #debian-python that Python(2) and > Python 3 are sufficiently different that they should be treated as essentially > separate run time systems. If a package expresses support for Python versions > greater than (for example) 2.4, this should never include any Python 3 > versions. Your mail doesn't seem to mention the planned python-foo/python3-foo duplication for modules that are portable to both versions of python. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktimaz8owqmc11fogtfgpvgqmsjcy-qcypg8ro...@mail.gmail.com
Re: Proposed Email to the release team about XS/B-P-V
On Thu, Jun 24, 2010 at 10:42 AM, Scott Kitterman wrote: > The email is meant to go to the release team to address what I understand to > be release team specific requirement. I think that the broader question needs > to be discussed in a broader audience. I think it is relevant there as well, IIRC folks from the then release team were behind the move from python2.X-foo to python-foo modules. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktimzqrdcbyxlmafqa12t5npj4xbvze75d3skj...@mail.gmail.com
Re: python 2.6 deb for lenny ?
On Sat, Jun 26, 2010 at 1:19 AM, Toni Mueller wrote: > FWIW, I've just updated to 2.6.5. See > http://people.debian.org/~toni/python2.6/. > > The only thing I had to change was to set the libdb-dev dependency from > 4.8 to 4.7, but then, I only compiled on my workstation, which might be > infected with other backports already. I used libdb4.5-dev since that is what python2.5 uses in lenny. > If you want to make it more official, please step in and tell me what > your changes are. ;) I recently did a python2.6 backport and I also had to do these: Version the python-sphinx build-dep to use the version in lenny-backports. Install the version of python-central from squeeze. The software I wanted to run under python2.6 needed some C-based modules so I had to install the versions of those from testing since I was too lazy to rebuild them all. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktimobmur52ien5-vumqmsehb4ac2xsqcbddwm...@mail.gmail.com
Re: karaage
On Fri, Jul 16, 2010 at 8:03 AM, Brian May wrote: > On issue that has been nagging us - what is the best way to handle > python based config files? e.g. the settings.py file that is standard > for Django applications? This sounds like more of a question for the webapps list. My standard answer for webapps is that the package should not assume which URL it is installed at, not assume there will be only one instance of it and not assume where the sysadmin would like to keep uploaded user data. So you probably need dbconfig-common, wwwconfig-common and some debconf prompts to ask the sysadmin if the want to create an instance at install time and then ask appropriate questions about how many instances, which URLs they should be at and where on the filesystem or which database hosts to use. For stuff like automated database upgrades you can use a configuration file in /etc that lists all the instances to upgrade. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktingfk9zy1w4w_evoivmceaginxyumofiqdsi...@mail.gmail.com
Re: Packages whith “except” overwriting builtins
2010/8/3 Jakub Wilk : > You might be easily mislead into thinking that this code ... > will catch both IOError and OSError exceptions. In fact, it will not, as it > is more or less equivalent to: ... > There are about 50 packages in the archive whose developers make this kind > of mistake. I have attached log file and dd-list. I'm not willing to do MBF, > but if someone else is, please feel free to use my data. What about adding a lintian warning about this? Could file a bug about that? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktikuyt7zfxe-huedxyo7j-0+wecvjfrbqsj5m...@mail.gmail.com
Re: Packages whith “except” overwriting builtins
On Tue, Aug 3, 2010 at 10:50 PM, Tristan Seligmann wrote: > How would you implement the warning? There's no way to easily tell > whether a given name is an existing class name or not. Using whatever method Jakub used to create his list, if it is implementable in perl that is. Actually, is there any generalised syntax, language, deprecation and mistake checker for python? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktikky-8masnztum_2obd6c9wmhehbe0dj16d5...@mail.gmail.com
Re: Packages whith “except” overwriting builtins
On Wed, Aug 4, 2010 at 3:43 AM, W. Martin Borgert wrote: > There are pychecker, pyflakes, and pylint in Debian. > This specific case raises a warning in pylint, if I'm not mistaken. Thanks for the info, I've added these package names to the DebianMentorsNet wiki page listing feature wishlists for mentors.debian.net/lintian-extras. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktim83r9v3ekuwqrk1bkrn9rxhmhpchsw2q=ky...@mail.gmail.com
Re: Packages whith “except” overwriting builtins
On Wed, Aug 4, 2010 at 12:20 PM, Jakub Wilk wrote: > I checked only for built-in exception names, which should cover most cases. > A simple regex like: Thanks. > Also, feel free to file a bug against lintian. :) Done (#592379). This will probably end up as a wishlist against pyflakes and a pyflakes test for lintian extras. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktikypwsynwurn47noguwptbmzzy1rwbgoxefu...@mail.gmail.com
common issue: setlocale handling?
Hi all, I recently got a bug filed on iotop about its setlocale handling (#593846). With a quick grep of my system I can see code in the following packages that looks like they would probably have the same issue: python-xdg virt-manager virtinst iotop mercurial-common python-hachoir-metadata inkscape cython python-gmenu python-aptdaemon fontypython gmobilemedia Do any of the python code checkers have heuristics that can check for this? There was discussion at DebConf10 about having lintian run external programs to check for things like python coding errors and so on. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktingej4zwbttj+ez+ljlabug6g-e8vzbstbx0...@mail.gmail.com
Re: common issue: setlocale handling?
On Sun, Aug 22, 2010 at 3:40 PM, Jakub Wilk wrote: > I don't think this is a bug at all. I'd rather say it's an user error. I disagree, stuff written in C or Perl doesn't crash when the locale is not set properly and neither should stuff written in Python. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktimok8kfd5r9mflfesjh6x2ugtzjs=+lucco0...@mail.gmail.com
Re: Skip Python 2.6 and use 2.7 as default in Squeeze?
On Wed, Sep 1, 2010 at 6:33 AM, Marian Sigler wrote: >> Given how much work is required to change the default Python, does it >> make sense to just skip Python 2.6 and use 2.7 as the default Python >> version in Squeeze? > What has emerged here? I see that it won't be the default, but will it > be at least included at all? As you can see here, python2.7 is only available in experimental: http://packages.qa.debian.org/p/python2.7.html As we are now in the squeeze freeze period it is unlikely that python2.7 will enter squeeze: http://lists.debian.org/debian-devel-announce/2010/08/msg0.html > For most python users (I assume) it will be of great benefit already if > just pure python without all those packages debian provides would be > available (also) in version 2.7. backports.org exists for packages needed by users of stable/squeeze that weren't yet ready for inclusion in testing/squeeze at the time of the freeze. It would probably be a good idea to use it for python3.2 and python2.7 packages once squeeze is out. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktimj9bkg7br6wirbu7ry5gk9d=f9kgkl3jmwv...@mail.gmail.com
Python 2.6 release candidate in squeeze?
Hi all, Looks like python2.6 2.6.6-3 was intended for sqeeze, is that the case Matthias? A summary of the changes: Two new upstreams (rc2 and final 2.6.6) One RC bug (#590138) One CVE (CVE-2010-1634) Two regressions (upstream #8688, LP #615240) Disabling some tests http://packages.debian.org/changelogs/pool/main/p/python2.6/current/changelog -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktimrzkw-rckxbma5copoqz_ma-udadazmtmta...@mail.gmail.com
Re: common issue: setlocale handling?
On Mon, Aug 23, 2010 at 8:17 PM, Barry Warsaw wrote: > My guess is that you'd get a lot of push back from folks in python-dev. Won't > a change like this have the potential to produce confusing, wrong, or hard to > track down bugs? This kind of implicit behavior change seems to run counter > to the "explicit is better" mantra. > > Note too that there's no way this would change before Python 3.2. > > I'm not qualified to personally champion this upstream, but I do encourage you > to submit a bug at bugs.python.org if you feel strongly about it. If you > can't or don't want to bring it to the attention of python-dev, I will do so > in a neutral way. I missed your mail due to an evil mail provider, but it looks like doko has filed a bug about this: http://bugs.python.org/issue1703592 Some particularly insightful comments by cjwatson there. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktikixsueiu+pzudtfr0epgpfmzvaz+jkuyg0u...@mail.gmail.com
Re: question about packaging a python-based software that ships a shared object library file
I'm doing what you propose with fonttools and I like the solution. If upstream is shipping it as a private extension, keeping it that way is a good idea. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlkti=sbzrb5for5cukkd9nzkjpfvm422xcflwux...@mail.gmail.com
Re: Untrusted search path vulnerabilities
> On Wed, Nov 17, 2010 at 22:58, Jakub Wilk wrote: >> A number of packages in the archive sets the PYTHONPATH environment variable >> in an insecure way. They do something like: >> >> PYTHONPATH=/spam/eggs:$PYTHONPATH >> >> This is wrong, because if PYTHONPATH were originally unset or empty, current >> working directory would be added to sys.path. I wonder if this class of vulnerabilities (inc the LD_LIBRARY_PATH ones) could be automatically warned about by lintian. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktinjdtuqd5mogcccphroabv+4vp4lfbqzjukr...@mail.gmail.com
Re: Packaging Django applications and projects
On Tue, Mar 8, 2011 at 9:50 PM, Zygmunt Krynickiu wrote: > I'd like to define and document the recommended best practice of packaging > Django 1.0+ (and especially 1.3) web applications and projects for Debian. I > started this on the Debian wiki at > http://wiki.debian.org/DjangoPackagingDraft Some things I (as a sysadmin user of Debian) would like to suggest for all web apps, django based or not: Use debconf to ask if the sysadmin wants to setup a site and then ask for enough detail to do so. The package should ship a script that can be called either manually by the sysadmin or automatically by the maintainer scripts (using debconf answers) to setup a site or a sub-path of a site. Database (with South etc) and configuration upgrades (with Config::Model or similar) are great, please do them as automatically as possible after confirmation using debconf and or provide scripts for the sysadmin to do them. Data: I like to differentiate between data supporting the package and data that belongs to the sysadmin/site. IMO the former belongs in /var somewhere and the latter at a path chosen by the sysadmin. I don't think this is gotten right by much software, including by all database packages. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/AANLkTi=a8z16rwv9_iintjq_zzrzwf7mv2we-omfj...@mail.gmail.com
Bug#622239: RFP: python-iview -- alternative frontend to ABC iView
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-python@lists.debian.org * Package name: python-iview Version : 0.2 Upstream Author : Jeremy Visser * URL : http://jeremy.visser.name/2009/08/30/python-iview/ * License : GPL Programming Lang: Python Description : alternative frontend to ABC iView Python-iView is an alternative frontend to the ABC (Australian Broadcasting Corporation) iView, is an awesome ABC TV programme catchup service that lets you watch most ABC programs from the last month in your browser. Not only that, some Australian ISPs have unmetered the service so it doesn’t use up your download quota. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: list of package for python_support -> dh_python2 ?
On Fri, Jun 10, 2011 at 1:40 AM, Barry Warsaw wrote: > What is the process for deprecating python-support? Who makes that decision? Add a lintian warning saying that it is deprecated. Wait. File bugs on all packages using it. Remove it and anything still depending on it. The maintainer is responsible for declaring it is deprecated. Personally I've always wondered why a Debian-specific helper should be needed instead of python upstream behaving the way we wanted. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/banlktimbeyd1xxggymdf_z-oqbjzmcw...@mail.gmail.com
restarting processes when python libraries are upgraded?
Hi all, Since python doesn't keep .py files open its hard to use things like checkrestart to find out which servers to restart when upgrading a python library for security updates. I wonder if a dpkg triggers based mechanism could perform this function. Any thoughts? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/BANLkTim-6urdgU0rsUvmzBG6uL=amx1...@mail.gmail.com
Re: python2.7 as default: where are we? (Was: Bug#641207: ITP: ordereddict)
On Sun, Sep 11, 2011 at 11:38 PM, Luca Falavigna wrote: > Would it be possible to draw a map of things still to finish before > attempting to switch default to 2.7? There are a couple of resources > already ([0] and [1]), are there other useful bits around? The same as the release.d.o bug, but: http://dex.alioth.debian.org/dextools/projects/dex-ubuntu-python2.7/index.html Probably there are other Ubuntu patches to be looked at. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6gyu4xah7tudq+yrx_oxqen+yleuhxn+7woabqvbhg...@mail.gmail.com
Re: may be a logo?
On Thu, Sep 15, 2011 at 3:41 AM, Yaroslav Halchenko wrote: > Do we have a logo for our Python-In-Debian effort(s) (was needing one > for a recent talk but failed to deliver in time)? What about > having one? I am not a designer and possibly lacking any taste, so > please do not judge wildly. What would be your choice among the > following 6: > > http://www.onerussian.com/tmp/pydebian-red_tuned/ > > ? choice 0 == do not like any If the choice of a lurker counts, #2 I wonder if that is an allowed use of the Python trademark though. A similar combination of the GNOME foot and the Debian logo is apparently not allowed: http://lists.debian.org/1309267090.5023.15.ca...@novo.hadess.net -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6egvcogayqxacwvwuekb7e8cdckp_op7vxp6umwnyd...@mail.gmail.com
Re: Request for packaging - Nuitka the Python Compiler
On Thu, Oct 13, 2011 at 6:47 AM, Kay Hayen wrote: > Currently I am just trying to be a good upstream. On that topic, we have a bunch of good links and some Debian-specific information about how to be a good upstream here: http://wiki.debian.org/UpstreamGuide I would personally add "don't use SCons" that, simply because of my experience with an upstream who started using it; I had to re-implement a bunch of autotools features, starting with $DESTDIR. Not sure if it has improved since then. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6hrsmf8-0c3dukcn4ofmap9odhbsksq0gdw9pdc0w_...@mail.gmail.com
Re: Request for packaging - Nuitka the Python Compiler
On Thu, 2011-10-13 at 09:18 +0200, Nicolas Chauvat wrote: > If and only if you were to consider replacing SCons, take a look at > waf that has many qualities. http://code.google.com/p/waf/ Please do not look at waf, it is worse than scons, which is why it was removed from Debian. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Alternate way to contact Python-modules-team mailing list?
On Thu, Oct 20, 2011 at 12:51 AM, Paul Elliott wrote: >> returned was: 550 550-Blacklisted URL in message. (blackpatchpanel.com) in >> [black]. See 550 http://lookup.uribl.com. (state 18). If you read the error message you would have noticed that your blackpatchpanel.com domain has been blocked by uribl.com. I've previously had people complain about uribl.com blocking identi.ca and people not being able to mail alioth lists with that in their sig. Please contact the uribl.com folks about unblocking it and contact the alioth folks about not using uribl.com since they appear to be blocking complete domains instead of specific URLs. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6hlgds6pzrgly6xommpbw+yw_h0oqa0nj3gv_wk7eq...@mail.gmail.com
Re: Python 3 packaging
On Sun, Oct 30, 2011 at 2:05 AM, Thomas Kluyver wrote: > I've been having a go at repackaging some Python modules where I know the > same codebase can be compiled for Python 3. Any chance someone could update numpy for Python 3 (#601593)? I need it for testing a Python 3 patch for fonttools upstream. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6EG0CAy=kj5pif0t4dgh2p0g2zvzapdgiacalegwf3...@mail.gmail.com
Re: How do I add support for python3 to my package?
On Thu, Nov 17, 2011 at 7:55 PM, Stefano Rivera wrote: > Hi Paul (2011.11.17_12:05:46_+0200) >> I created a package with py2dsc. After some tweeks, it works correctly. The >> upstream says package also works with python 3. How do I alter my source >> package to also produce a python 3 version? > > That's currently non-trivial, and certainly not in the realm of things > py2dsc can safely do, yet. > > Basically, you'd need to override all the dh_auto_* rules to loop over > all supported python2 and python3 versions. > > If you don't need the python3 version, yet, I'd ignore this until the > tools improve. Would dh --with python2,python3 not work? I've seen that in some packages IIRC. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6hugdalwehd7m4ujkjqu8yehtyybho3r7x3hct0soq...@mail.gmail.com
Re: "search.html doesn't look like a Sphinx search page"
On Fri, Feb 24, 2012 at 6:53 AM, Jakub Wilk wrote: > Also, please remove Google Analytics code, and references to other > JavaScript code and CSS hosted on external websites. I don't want to be > tracked when viewing local documentation. :< That sounds like an RC bug; things in main depending on stuff not in Debian. I wonder if we need some lintian warnings about this sort of thing. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6fr88n9m5ns5oi-g0otfqesveswcphwoggj1vnnx--...@mail.gmail.com
Re: "search.html doesn't look like a Sphinx search page"
On Fri, Feb 24, 2012 at 8:13 PM, Pietro Battiston wrote: > If there is consensus (and I guess it would be good to find it), I > wasn't able to detect it... > http://lists.debian.org/debian-mentors/2011/05/msg00194.html > > Notice I _did_ provide locally some javascript libraries which (the > upstream downloads remotely, and which) are required for the > functionality of the documentation. I would say that Debian Policy 2.2.1 constitutes consensus: http://www.debian.org/doc/debian-policy/ch-archive.html#s-main Please report RC bugs where you find this issue. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6EKtcOAsPYx2+u1N=gpmkxa_etygvvxbyrsyosjglj...@mail.gmail.com
Re: warning: symbol PyLong_FromUnsignedLong...
On Wed, Apr 11, 2012 at 11:43 PM, Mathieu Malaterre wrote: > I am trying to remove the remaining warnings from the gdcm/python > package. They can be seen here: That is pretty normal for plugins on Linux; the symbols are provided by the program that loads the plugins and the plugins do not reference where they get those symbols from. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6gkzs6dqjrgervvo4mig8wobl7fzsqqcalkehy2iwx...@mail.gmail.com
Re: warning: symbol PyLong_FromUnsignedLong...
On Thu, Apr 12, 2012 at 3:04 PM, Mathieu Malaterre wrote: > I am trying to remove the annoying 'todo' section of the gdcm package page: > > http://packages.qa.debian.org/g/gdcm.html > > If this was a lintian false positive, one would use > *.lintian-overrides file. However in this case I did not know what I > need to do. Since every single python module suffer from this, I > thought there would be something very simple. Based on my reading of dlopen(3) and the output of objdump -T /usr/bin/python, dpkg-shlibdeps needs to look for defined symbols in executables too. Since there is no way to know exactly which binary a symbol is supposed to be supplied by (no SONAMEs in binaries), this will be a bit tricky to get right. If you want to implement this, good luck! -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6escv1r8vlg_megdbrf3gv_ikg5dcovdjg7p75yspo...@mail.gmail.com
Re: pythonX.Y maintenance team
On Fri, Apr 13, 2012 at 9:26 PM, Scott Kitterman wrote: > times when the only 'solution' available is a short term hack that's needed > for Ubuntu's time based release schedule that isn't appropriate to Debian's > approach of doing things right and releasing when ready. Why are short term hacks OK in Ubuntu? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6H3fJtvsPnJzapn8gQ0acV=bbc_3f0nts4hktju3cp...@mail.gmail.com
Re: how to take a public package private?
On Sat, Apr 28, 2012 at 10:54 PM, Paul Elliott wrote: > I mean move it from the standard place, to a package specific place. > I mean move it to a package specific directory. Michelle seems to be confused. Michelle was talking about the location of the binary and source packages, rather than your original question about the location of .py files inside of a binary package. Hopefully someone else will answer your original question. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6epyf665f4juoodsrovz0-y4vos2bakqysq3dabezi...@mail.gmail.com
Re: Porting UberWriter to Debian
On Mon, Sep 24, 2012 at 5:07 PM, Hadret wrote: > I'm working on packing UberWriter (http://lauchpad.net/uberwriter) > software. Basically everything is working flawlessly, except one file: > locales.db. I'm using plain dh_python2 to build the package and this > is the only file, which isn't provided where it should: > > 1. It should go to /usr/share/pyshared/uberwriter_lib/thirdparty/pylocales Third-party stuff should be packaged in separate source packages, not in uberwriter. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6EQbngoq-mwbSs0_DNRdkL+SS=6Kjo5=bz33xn40ot...@mail.gmail.com
Re: PyCon 2013 -- tentative title/abstract/outline -- feedback plz
On Fri, Sep 28, 2012 at 9:47 PM, Paul Tagliamonte wrote: > ^^ this is a great idea. It'd be nice if we could prototype a flake8 / > pyflakes run against the archive, and filter for serious errors We did do that at one point with pyflakes: http://qa.debian.org/daca/pyflakes/sid/ Unfortunately no-one has been working on DACA recently, hint hint ;) -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6H-2qFzfogumqVke+G7=nbm2rvm6mnrr8axplnu4+d...@mail.gmail.com
Re: Solving the multiarch triplet once and for all
Seems like a lot of effort when there is no /usr/bin//python so there can be only one arch of python installed anyway. What are the use-cases for python multiarch? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6e4zf_3fu4ph5mqjf3yhcthtc9rwf+ozvbjdpwdhhw...@mail.gmail.com
Re: Solving the multiarch triplet once and for all
On Wed, Dec 19, 2012 at 12:29 AM, Dmitrijs Ledkovs wrote: > cross-compiling the archive / cross-bootstrapping the archive for a > new architecture. I suppose cross-compiling will be useful but I didn't think python was part of the build-essential set that must be cross-compilable, is that actually the case? PS: I'm subscribed. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6hkanjztu+a7ugzr-ztampx5r50aqxjtd0q5d6zbw9...@mail.gmail.com
Re: How does team maintenace of python module works?
On Thu, Feb 21, 2013 at 12:37 PM, Scott Kitterman wrote: > That's the sort of thing that convinces me it's too hard. The fact that I > have to manually make the association between individual local and remove > branches is just insane. This has changed with git from experimental, it sets up the association by default for remote branches and gives you an option to turn it off or turn it on for local branches too. Theres an option to set branches to use rebase by default too. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6h9n-saggbhr6tydeddtqqsbqyufmxhtenn7vo+uh_...@mail.gmail.com
Bug#701222: RFP: dnsgraph -- trace and graph all resolution paths for DNS names
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-python@lists.debian.org * Package name: dnsgraph Upstream Author : Dennis Kaarsemaker * URL : https://github.com/seveas/dnsgraph * License : MIT Programming Lang: Python Description : trace and graph all resolution paths for DNS names dnsgraph depends on python-whelk by the same author: https://github.com/seveas/whelk -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#705339: RFP: python-pyephem -- scientific-grade astronomical computations for Python
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org, debian-python@lists.debian.org * Package name: python-pyephem Upstream Author : Brandon Craig Rhodes * URL : http://rhodesmill.org/pyephem/ * License : GPL/LGPL Programming Lang: C, Python Description : scientific-grade astronomical computations for Python I would like to schedule some cron jobs relative to the time of sunset and sunrise at my current location, having this package in Debian would allow me to do that. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: how could I help?
On Sat, Jun 15, 2013 at 6:40 PM, Stéphane Blondon wrote: > Do you think I could help? If yes, how? A number of parts of Debian infrastructure are written in python, if you wanted to help out our core teams by writing python that would be great. There are dak (ftp team), ud (sysadmin team), various QA bits, the security tracker (security team) and probably more that I can't think of right now. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6hvkm_94vrk2plzcq0yv_84gde9cnefbpsfhj6av7e...@mail.gmail.com
Re: Inconsistency in source package naming for python modules
On Thu, Jul 11, 2013 at 3:54 AM, Thomas Goirand wrote: > Oh, I need this pyX package... Let's download it. I assume here you mean "I need whatever package provides 'import pyX' for python"? If so this is solvable using something like DEP-11 that maps package names to things that they provide (shared libs, manpages, python modules, fonts, glyph ranges, info pages, hardware support, applications etc). The idea isn't yet finalised or implemented but there is some info here: http://wiki.debian.org/DEP-11 I imagine the way it will work is something like this: apt-get install component:python:pyx -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6HL9TRaL9Y1Zsu4=kg9ottzmvw0nwvmyhbs_+uotmt...@mail.gmail.com
Re: Inconsistency in source package naming for python modules
On Fri, Jul 12, 2013 at 12:22 AM, Thomas Goirand wrote: > I've seen both cases in the archive! DEP-11 FTW. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6E-E-8f0ue1h6cRu3PkEw3mj=ctJmNM5duCeDXgD=8...@mail.gmail.com
Re: PEP 453 affects Debian packaging of Python packages
We don't do "private copies" or "bundled copies" in Debian, so I guess the right way to go for Debian is to have python depend on python-pip and python3 depend on python3-pip? http://wiki.debian.org/EmbeddedCodeCopies -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6gru1so8feclepdxbnyzfshuzjwlo6t6cx-poxrbit...@mail.gmail.com
Re: PEP 453 affects Debian packaging of Python packages
On Wed, Sep 18, 2013 at 4:33 PM, Scott Kitterman wrote: > P.S. I'm not nominating myself to be the diplomat that talks to upstream for > what are probably obvious reasons. Too late, upstream folks (for eg Barry Warsaw) are on this list, are DDs and are part of the Debian Python community so you already became our diplomat :) Barry, I hope this thread has not annoyed you at all :) -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6ExYyp22ugLTZV3A4mxWSH2y191-bSWh=se8c8c4y1...@mail.gmail.com
Re: about python-oauth2: CVE-2013-4347
On Wed, Oct 9, 2013 at 5:46 AM, Philippe Makowski wrote:
> do you think that for fixing that, using
>
> return ''.join(random.choice('abcdefghijklmnopqrstuvwxyz123456789') for
> i in xrange(length))
...
> would be an acceptable fix ?
No, from the announcement of this issue on oss-sec:
... the Python 'random' documentation clearly states the results are
repeatable ...
http://www.openwall.com/lists/oss-security/2013/09/12/5
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
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/caktje6fsygkcqy56grukxwcbrkxbt2m5f9apawu0c+d-jok...@mail.gmail.com
Re: Using ‘export http_proxy = http://127.0.9.1:9/’ to fail noisily on dependency problems
On Tue, Oct 15, 2013 at 1:47 AM, Thomas Goirand wrote: > I've read multiple times that they do. Could you show a build log where > something is downloaded? At around 24:30 in the DebConf13 cross-compiler BoF a discussion about -source packages, build-depends on foo:src/foo:build-deps and apt-get source during builds was started. At 28:28 Helmut Grohne claimed that there is a plan to enable network namespaces on the Linux buildds and afterwards it was claimed by Colin Watson at 28:48 that some parts of d-i rely on being able to download stuff during the build and would be broken by that. No idea which package he meant though. https://penta.debconf.org/dc13_schedule/events/1020.en.html http://meetings-archive.debian.net/pub/debian-meetings/2013/debconf13/webm-high/1020_Cross_compilers_in_Debian.webm -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6FbdKh9=upenhe4qjgo4v_0x_l1-1nipefezg3m3xv...@mail.gmail.com
Re: Packaging AngularJS application as part of the python twisted application
On Wed, Oct 16, 2013 at 7:54 AM, Ben Finney wrote: > I think we're going to have to (as the Debian Python community? as the > broader Debian maintainer community?) come up with a unified approach to > dealing with the rapidly increasing tendency for upstream releases > bundling doing this. Upstream bundling happens in too many different ways to deal with that in any way other than to push back every time an upstream wants to add yet more embedded code copies[1] to Debian. Tell them to do things in a sane way otherwise we can't add their stuff into Debian. Tell them to read the upstream guide (and update it if need be). Tell them to release proper source tarballs that are exactly the same as their VCS. Tell them to not commit generated files to their VCS. Tell them to never include copies of their dependencies in their VCS. Tell them to switch from systems without sane repository and dependency systems (such as Android, MacOS X and Windows) to GNU/Linux distributions like Debian. Tell them to think about sysadmins before themselves. http://wiki.debian.org/EmbeddedCodeCopies http://wiki.debian.org/UpstreamGuide -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6ehwzs8n1ecab4t2cdkcbupm+uabkok-n2lrd0ayfr...@mail.gmail.com
Re: uninstalling issue of a local Debian package
On Mon, Oct 28, 2013 at 1:52 AM, Florian Rothmaier wrote:
> I'm an astro-physicist working for the Virtual Observatory project at
> the University of Heidelberg.
Awesome!
> What is the reason behind this issue?
It sounds like your prerm is missing the code needed to delete the
.pyc files. For dh_python2 this looks approximately like the code
below. On the installed system, take a look at
/var/lib/dpkg/info/python-gavodachs.prerm or in the build directory
after a successful build, look at
debian/python-gavodachs/DEBIAN/prerm.
# Automatically added by dh_python2:
if which pyclean >/dev/null 2>&1; then
pyclean -p iotop
else
dpkg -L iotop | grep \.py$ | while read file
do
rm -f "${file}"[co] >/dev/null
done
fi
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
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/caktje6fvdy0cnvjldsklw+51twzftuktxxm6trp1fhce4-2...@mail.gmail.com
Re: Best practice: exclude generated ‘foo.egg-info’ files from source and VCS
On Mon, Nov 25, 2013 at 5:55 AM, Ben Finney wrote: > Since Distutils is the officially supported standard for Python It is probably about time it were demoted from that. Not supporting dependency information in a useful way is not really acceptable today. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6FoyxKyMgrb5DCq4xTGTu2=pccejmddjhe7vp+wbnq...@mail.gmail.com
Re: Recommending get-orig-source for packages ?
On Tue, Dec 3, 2013 at 11:42 PM, Olivier Berger wrote: > I haven't spotted anything recommending a get-orig-source target in > debian/rules in the team's docs. Policy recommends it, that should be enough? http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6emu_h+mozqo880+ktxembfuorceisyw6u0nogojrk...@mail.gmail.com
Re: Recommending get-orig-source for packages ?
On Wed, Dec 4, 2013 at 10:36 AM, Stuart Prescott wrote: > tl;dr: is get-orig-source supposed to be a duplicate of uscan (d/watch) or > apt-get source? Neither. As policy attempts to explain, get-orig-source is for the cases where the Debian orig tarball is not bit-for-bit identical to the upstream tarball. If you have a debian/watch file, get-orig-source is pointless. A get-orig-source target is only useful for documenting (and automating) how to convert upstream sources (in git/hg/tarballs/whatever) into Debian orig tarballs. uscan will never be flexible enough to deal with every upstream so I think the right ways forward are: Add support for more sites to [1]. uscan to grow features for removing files from upstream tarballs, in a declarative way preferably. The default dh get-orig-source to invoke uscan if debian/watch is available. Policy to define get-orig-source more clearly. Re version numbers, I can see use-cases for both getting the current as from debian/changelog and the latest available. So a standard way to pass a version, which could be 'current' or 'latest' or another version would be the right thing to do. Personally I also feel that debian/watch and get-orig-source need to be maintained outside the packaging, probably somewhere like the new PTS (tracker.d.o) once that is up, running and has more contributors. 1. http://anonscm.debian.org/viewvc/qa/trunk/cgi-bin/fakeupstream.cgi?view=markup -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6hcfkma6+ygyhpuge_bto_3pftrd_dxbej1eqawn-u...@mail.gmail.com
Re: Recommending get-orig-source for packages ?
On Wed, Dec 4, 2013 at 3:43 PM, Andreas Tille wrote: > That's in devscripts git and will be included in the next devscripts > version. (see [1]) Awesome, thanks for your work on that. That said, the choice of debian/copyright as the location for files to be excluded seems awkward/weird. I would have chosen debian/watch myself. > Is it??? http://lists.debian.org/20131203194424.ga26...@gmail.com -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6fds-rmwcn1xaurvsyiddnfxbfoqzfnler9oyyzn6m...@mail.gmail.com
Re: QA Developer overview, compared with PET
On Mon, Jan 27, 2014 at 7:37 AM, Ben Finney wrote: > Thanks for bringing PET to my attention. But I wonder whether it's > unused for good reason? The only reason it is unused is people don't know about it or forget it exists. > What does PET do which the Packages Overview tool does not? It looks at the VCS repositories too. > Why advocate PET rather than advocating for those features to be added > to the QA PAckages Overview tool? PET works now and there are few people working on QA infrastructure so DDPO is unlikely to have many features added. DDPO is also horrible PHP code which probably discourages contributions. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6e+wzot2io_ggakxynqkzt-zwpj0dvjosvnxjgv_fp...@mail.gmail.com
Re: Future of django-pagination in Debian
On Wed, Feb 12, 2014 at 11:02 AM, Andrew Starr-Bochicchio wrote: > Any one have any opinions? How does the upstream Django community recommend to do pagination? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6EzdGGZ-860=3eRC=5rn-oztuxbdajex3pok7ohx_7...@mail.gmail.com
Re: RFS: Pyspread 0.2.6-1
On Tue, Feb 18, 2014 at 7:48 PM, Andreas Noteng wrote: > Pyspread works just fine without ttf-mscorefonts-installer, so I guess > suggests would be a better choice anyway. The tests will fail without the > package though. Is it OK to include ttf-mscorefonts-installer as a test > dependency in debian/tests/control ? Why does the test need a particular font? -- bye, pabs http://wiki.debian.org/PaulWise -- 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/CAKTje6FW-QVMonULBT5wN6QR7s1oK+jo6_=ygbojkj0xred...@mail.gmail.com
Re: Python 3.4 and ensurepip (rehashed, long)
On Thu, Mar 20, 2014 at 5:40 AM, Barry Warsaw wrote: > I: Should we follow Fedora? > > Fedora is discussing some of these issues too[6]. Looks like one of their > devs created an rpm->wheel conversion script so that if you pip install a > package from the archive, it'll get the rpm, convert it to a while and install > it in the virtual environment (IIUC). I don't much like that, so I don't > suggest we take that approach. Side-note: DEP-11 should make it possible to do something like this in Debian to get the python-foo Debian package installed: apt-get install --component python:foo https://wiki.debian.org/DEP-11 -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6HcYST8stEcE51vWdDjgfAh2XQo66N6Nw=ccytpay7...@mail.gmail.com
Re: favouring Python3 in the Debian policy
On Wed, May 7, 2014 at 10:45 PM, Matthias Klose wrote: > Attached is a proposed change to the Debian Python policy to focus on Python3 > within the distribution. The intent is to document and start a large journey > towards one Python stack in Debian. This is unlikely to happen for jessie+1, > but > we should state the plan now so that it doesn't come later as a surprise. I'd like to suggest: A bits from Debian Python mail on d-d-a mentioning this. lintian tests, pedantic level for now. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6E5m6yJbFGDuzinuRVYqzraLGX+xT8R88xNPPP=eue...@mail.gmail.com
restarting services after security upgrades in pure-Python modules?
Hi all, Anyone know if it is possible to detect processes that are using old versions of pure-Python modules after security upgrades to them? -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Embedded six.py in many packages: can someone add a lintian check?
On Thu, May 29, 2014 at 10:53 PM, Barry Warsaw wrote: > One of the things I want to add to my mythical PEP are at least declarations > of vendored packages. What tool do people use to do vendorising? Maybe that could be patched to include a file containing info about which projects were vendorised. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6hanarhjo+ltl6tqsccnbmagtq79t89nxyyvdgwuak...@mail.gmail.com
Re: Embedded six.py in many packages: can someone add a lintian check?
On Thu, May 29, 2014 at 11:13 PM, Barry Warsaw wrote: > On May 29, 2014, at 10:58 PM, Paul Wise wrote: > >>On Thu, May 29, 2014 at 10:53 PM, Barry Warsaw wrote: >> >>> One of the things I want to add to my mythical PEP are at least declarations >>> of vendored packages. >> >>What tool do people use to do vendorising? > > AFAICT it's mostly `$foreignvcs pull; cp -a; $myvcs commit`. > > So not very helpful. ;) What about encouraging often-vendorised projects to include a comment like "Project: foo" in their __init__.py? Then lintian could detect if there are multiple projects in one tarball. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6hfj9xvfwclsdsd_wcqnhaq596fmgbfjvkmmgiy8by...@mail.gmail.com
Re: RFS: python-rarfile/2.6-1 [ITP] -- RAR archive reader module for Python
On Tue, Jun 10, 2014 at 4:21 AM, Hugo Lefeuvre wrote: > It builds the python-rarfile package, which provides an RAR archive > reader module for Python. More informations can be obtained from the > following URLs: I don't intend to sponsor this but here are some comments: It looks like upstream is using the unrar command-line utility. The unrar that supports recent RAR files is non-free and the FLOSS version of that only supports old RAR files. Please ask upstream to switch to the unar (no this is not a typo) command-line utility instead, which is both FLOSS and supports recent RAR files. I would say this package should not enter Debian without that, otherwise it will encourage users to use non-free software. None of the comments in debian/rules are needed. You have chosen a different license for debian/* than what the upstream code uses. I suggest using the same license as upstream. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6HiiNn=t-sgbbpw2sanypzuhcbolk_ltbo6261xc72...@mail.gmail.com
Re: Upload of python-networkx 1.9
On Wed, Jun 25, 2014 at 3:41 PM, Thomas Goirand wrote: > * New upstream release (Closes: #750233). I think you meant this instead: * New upstream release - Fixes test failures (Closes: #750233). https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-debian-changelog -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6eohzjttz4anqrrfkf+2tdyao_gw9ahaf4fvyvhpd3...@mail.gmail.com
Re: Passing arguments to nosetests in debian/rules:override_dh_auto_test
On Mon, Jul 7, 2014 at 2:45 AM, Josue Ortega wrote: > How can I pass them? and which is the right way to do it? According to the nosetests manual page the right way to do it is for upstream to delete the options from the Makefile and from travis.yaml and put them in a [nosetests] section in the setup.cfg file. Please read the manual page and send them a patch to do that. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6HVO+REozgZ+Y9ZLMmX9WOEv2YuPMk=zjcqjvvvg49...@mail.gmail.com
Re: apache2.2 / apache2.4 config
On Thu, Jul 17, 2014 at 9:11 AM, Brian May wrote: > Anyone got any better ideas? Something like this for the configuration: /etc/apache2/conf-available/someconf-2.x.conf: # All the common config options here /etc/apache2/conf-available/someconf-2.2.conf: Allow from all Include /etc/apache2/conf-available/someconf-2.x.conf /etc/apache2/conf-available/someconf-2.4.conf: Require all granted Include /etc/apache2/conf-available/someconf-2.x.conf Something like this for the postinst: if [ -x /usr/sbin/a2enconf ] ; then a2enconf someconf-2.4 else ln -sf ../conf-available/someconf-2.2.conf /etc/apache2/conf.d/someconf-2.2.conf fi -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6ENy03=8CJar-TtPVTpoSNAmgx0EbpTZ59iefQRd=w...@mail.gmail.com
Re: Help with old mathplotlib API (nxutils) needed
The mathplotlib API changes document recommends switching from matplotlib.nxutils to matplotlib.path.Path.contains_point and friends. http://matplotlib.org/api/api_changes.html#id1 Also I used codesearch.d.n and found some code which supports both versions of the mathplotlib API: http://sources.debian.net/src/psychopy/1.79.00+git16-g30c9343.dfsg-1/psychopy/visual/helpers.py#L41 http://sources.debian.net/src/psychopy/1.79.00+git16-g30c9343.dfsg-1/psychopy/visual/helpers.py#L362 http://sources.debian.net/src/psychopy/1.79.00+git16-g30c9343.dfsg-1/psychopy/visual/helpers.py#L405 -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6H9WJ8gp-0UVxgD6GwYa=ns_1slx3zicboucmbnq0q...@mail.gmail.com
Re: Speech Input
On Sat, Jan 10, 2015 at 6:19 PM, chaitanya sai alaparthi wrote: > ... takes the help of google speech recogniton api ... This means that the software relies on proprietary software and transmits user data over the Internet to Google. If you put this in Debian it will have to go to contrib and it should inform the user that their data will be sent to Google. -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6hm1cpb0vk++xwjyprioopnajmgs5lmrsrjz-jftbe...@mail.gmail.com
Re: Debian uscan redirector for PyPI (was: PyPI and debian/watch)
On Thu, Feb 5, 2015 at 6:53 AM, Tianon Gravi wrote: > Checking out http://pypi.debian.net/hy, it looks pretty easy to use. :) Could someone document this on the debian/watch wiki page please? -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6gab69_i-fypbceyfgiwirncb4ei2nerlefzwunbvf...@mail.gmail.com
Re: Debian uscan redirector for PyPI (was: PyPI and debian/watch)
On Thu, Feb 5, 2015 at 6:53 AM, Tianon Gravi wrote: > Checking out http://pypi.debian.net/hy, it looks pretty easy to use. :) Could whoever created this add a page to the Debian services census? https://wiki.debian.org/Services -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6fj8qeq3qegfiec0orrti2lv2mhcmjkdhtvkqhon8u...@mail.gmail.com
Re: Python 2 d-d-a proposal
On Thu, Apr 16, 2015 at 4:48 AM, Scott Kitterman wrote: > You might also ask Debian teams using Python in the Debian infrastructure to > review their packaged dependencies and identify any that aren't available for > Python3. We'll need to know that soon so we can work on porting > dependencies/finding alternatives. I think we should have as a goal for > Stretch (that's the next one, right?) to have all the packages in place needed > to run python using Debian infrastructure on Python3. That'll leave some time > then 'just' to port the Debian specific stuff. For services hosted on DSA machines, you can find the known dependencies in this file: https://anonscm.debian.org/cgit/mirror/debian.org.git/tree/debian/control This is missing dependencies DSA doesn't know about, services on alioth.debian.org, debconf.org and many debian.net services though. If you build the debian.org meta-packages and install them in a chroot, you should be able to get an idea of which Python 2 modules are needed for services hosted on DSA machines. -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6gpnmf6xzrd6qp3ry-6nfwpnw25ndi+vnouwvk+xnc...@mail.gmail.com
Python and Debian infrastructure
In addition to the Python 3 related work: Port service dependencies to Python 3. Port service code-bases to Python 3. We also need to: Port Django based services to Django 1.7 Port services based on Pylons (deprecated) to something else like Django: snapshot.debian.org debexpo (mentors.debian.net) debshots (screenshots.debian.net, in progress to Rails) debianmemberportfolio (portfolio.debian.net) Does anyone know of any other deprecated Python stuff that we should move away from? -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6hkht1l2v9veyj3rtwq0w65t4awuoemaxub1tucylh...@mail.gmail.com
Re: Python and Debian infrastructure
On Thu, Apr 16, 2015 at 10:48 PM, Jan Dittberner wrote: > Pyramid is a bit more lightweight Flask might be another option for lightweight framework needs. > Paul already suggested to merge debianmemberportfolio with db.debian.org but > I did not have time to evaluate that option yet. That is another rewrite that is in progress: https://anonscm.debian.org/cgit/mirror/userdir-ldap.git/ https://anonscm.debian.org/cgit/mirror/userdir-ldap-cgi.git/ https://github.com/LucaFilipozzi/ud/ Not sure when ud will be complete enough to deploy, but it uses Django. -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6f6crcjqeo-eelfchcxx8rgrcdtdhperjtbknkhcwq...@mail.gmail.com
Re: Offer to help with Python 2 porting
On Fri, Apr 17, 2015 at 10:10 AM, Bryan Shook wrote: > I saw Paul Tagliamonte's post to the debian-devel-announce list. I'd be > interested in assisting with this project. I wrote some ctypes Python code > that interacted with a Windows DLL. I ran into a lot of String encoding > situations with that. This would be my first time as a contributor to > Debian, but I'd love to be of service. I've joined this list, so let me > know where to start with contributing. Paul has created a new list for the porting effort, please subscribe there: https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6ek6krorg7xt0pj2t8yxbttxcvg-pozda8fmss9sov...@mail.gmail.com
Re: Sphinx 1.3 in Debian experimental
On Tue, Jun 30, 2015 at 4:14 AM, Barry Warsaw wrote:
> Maybe upstream would accept a patch similar to what I've done before. It
> could map |today| to the value of an environment variable, if it's set.
> E.g. something like SPHINX_TODAY. Then pybuild, dh_python{2,3}, or some other
> infrastructure piece could set that to the parsed changelog value. Generally,
> it wouldn't be set, so |today| would have the normal semantics.
|today| sounds like a misfeature, more interesting would be |version|
or |source_date|.
--
bye,
pabs
https://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CAKTje6Hf3+bK32PcF+mrNZ=0v9wcq+4z7yup-8zp27acpar...@mail.gmail.com
Re: Dealing with flit -- a simplified packaging of python modules
On Sun, Sep 20, 2015 at 12:47 PM, Thomas Kluyver wrote: > However, my hope in that sentence was that other packaging will come not > to rely on Python sdists containing a setup.py file. Using sdists for > Debian packaging is already somewhat dubious, because they can contain > generated and bundled files (we do both for Jupyter Notebook sdists). Source tarballs containing generated/bundled files is a bug that should be fixed. -- bye, pabs https://wiki.debian.org/PaulWise
Re: Dealing with flit -- a simplified packaging of python modules
On Thu, Sep 24, 2015 at 1:17 PM, Thomas Kluyver wrote: > That's my point ;-). From our upstream point of view, it's not a bug > that the distributions we put on PyPI contain generated/bundled files - > we do it that way deliberately, so that end users can install without > needing Javascript developer tools to build those files. If you want a > pure source tarball without generated files, that's available from > Github. Why are end users using source packages instead of binary packages and then complaining that the source tarballs aren't ready-to-run binary packages? -- bye, pabs https://wiki.debian.org/PaulWise
Re: Dealing with flit -- a simplified packaging of python modules
On Fri, 2015-09-25 at 19:25 -0400, Donald Stufft wrote: > Because the way Python packaging currently is and historically has > been, binary packages are not something that is widely available or > viable. Hmm, I thought eggs have been around for ages (seems about 8 years)? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Dealing with flit -- a simplified packaging of python modules
On Sat, Sep 26, 2015 at 5:21 AM, Donald Stufft wrote stuff Thanks for the summary, it sounds like the Python community is slowly moving towards a setup that is more closely aligned with Debian's values and setup. -- bye, pabs https://wiki.debian.org/PaulWise
Re: get started with building own packages
On Fri, Oct 2, 2015 at 1:48 PM, Cornelius Kölbel wrote: > At the moment I have a package > > privacyidea-apache2 and privacyidea-nginx, > which both require python-privacyidea, the webserver, database... An alternative might be to depend on httpd, dbcommon-config and then on package install, detect which web server is available, prompt the sysadmin for the relevant config info and generate the relevant web server and application configuration. -- bye, pabs https://wiki.debian.org/PaulWise
Re: get started with building own packages
On Fri, Oct 2, 2015 at 4:04 PM, Cornelius Kölbel wrote: > Ah, so apache2 and nginx provide httpd. I was not aware of this. Yes, along with a lot of other web servers. You could also just depend on apache2 | nginx since there is no way to generate configuration for all web servers and you probably don't want to spend time doing that yourself. -- bye, pabs https://wiki.debian.org/PaulWise
