Re: team vs individual as maintainer

Quoting Piotr Ożarowski : [Barry Warsaw, 2015-10-07] * Team in Maintainers is a strong statement that fully collaborative maintenance is preferred. Anyone can commit to the vcs and upload as needed. A courtesy email to Uploaders can be nice but not required. * Team in

Re: Packaging Bokeh

On 2015-09-04 22:44, Diane Trout wrote: > I've made some limited progress trying to package Bokeh (BSD-3-Clause) Many thanks for working this! > I managed to get the version 0.9.1 from pypi installable. (Though since it > was > my own experiments I didn't remove the jquery / bootstrap

Re: RFS: python-simpy3/3.0.7+dfsg-1 [ITP]

On 2015-06-17 00:01, Larissa Reis wrote: After discussion on this list, I'm making the new simpy version a separate package (see thread starting from [1]). I still need a mentor to review and a sponsor for the package. Uploaded. Thanks for working on this package! I like, that people can move

Rename package? (Re: Request to join DPMT and RFS: python-simpy/3.0.7-1 [ITA])

Hi, sorry for the late reply: On 2015-05-02 03:07, Larissa Reis wrote: Changes since the last upload: * New upstream release (Closes: #729866) - Simpy 3 API is not compatible with Simpy 2. For information on porting from Simpy 2, see

Re: Python 2 d-d-a proposal

On 2015-04-15 16:27, Paul Tagliamonte wrote: I'd like to send an email to d-d-a asking that project to consider no longer creating new Debian tools in Python 2. Makes sense. I try to use Py3 whenever possible. Sometimes some libs are still missing, mainly when upstream is not very active. My

Remove Python 3 version of module to fix RC bug? (python-exif)

I just now don't have the time to look at bug #775609 (python3-exif doesn't work, RC). If nobody steps in, I would upload a new package w/o Python 3 support for jessie. Wheezy hat python-exif, but not python3-exif, so there is no regression for users of wheezy. Anyway, upstream made a new

Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

On 2014-10-12 14:49, Thomas Goirand wrote: Let's say there's a few more other people which were not accounted for and that were not at Debconf, those who prefers having upstream source code in the VCS are still the majority. And some weren't at Debconf and prefer to work with upstream sources.

Re: Fwd: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1

On 2014-09-23 22:29, Sandro Tosi wrote: there's some people who's subscribed to the commit ml, so getting all the changes done to our repos. Now, with the transition to git we are getting this: 135 emails for updating a package (and these are only upstream changes). Did you consider this side

Re: git-dpm vs gbp-pq: new upstream and patch refresh (long)

). So I'm not sure where switched from git-dpm came from? Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe

git (was: Making packaging Python modules fun again)

On 2014-01-27 00:14, Nicolas Dandrimont wrote: (a lot) I agree with everything. If somebody has time to update my packages to modern helpers, convert them from svn to git, or enable Python 3, please go on! About git: This needs clarification, e.g. will we settle on gbp? Shall our branch be

virtualenv --system-site-packages (was: PEP 453 affects Debian packaging of Python packages)

Quoting Barry Warsaw ba...@python.org: Sounds a lot like `virtualenv --system-site-packages` right? IMHO, --system-site-packages should be the default. IIRC, it was the default in squeeze (1.4.9), but is not anymore in wheezy (1.7.1.2). Opinions? -- To UNSUBSCRIBE, email to

Re: PEP 453 affects Debian packaging of Python packages

On 2013-09-20 13:52, Paul Tagliamonte wrote: It's not about keeping the libraries up to date, it's about keeping the applications up to date. ... Hell, we shouldn't even introduce a module unless it has an app using it. I tend to disagree here (slightly). Too me, it is very important, that

Disabling pip for root? (was: PEP 453 affects Debian packaging of Python packages)

On 2013-09-18 09:36, Paul Tagliamonte wrote: 1) pip isn't for global package management, for this is stupid. If we disabled root use of pip, I think we'd all be a bit happier. Very quick and very dirty patch attached. 4) Python modules from dpkg are borderline useless for developers.

Re: PEP 453 affects Debian packaging of Python packages

Quoting Matthias Klose d...@debian.org: Also the platform package manager should be the preferred way to install packages, not pip, so even a Recommends is a bit strange. Yes, a not-recommended field would make sense here. As a passionate pip hater I would go for a Conflicts, which finally

Re: Two binary from one source - how?

Quoting anatoly techtonik techto...@gmail.com: Nice. But how do you create these install files? Can stdeb tool help with that? I don't know stdeb, but install files are easyly understood. See the documenation: http://www.debian.org/doc/manuals/maint-guide/dother.en.html#install (We're

Re: Two binary from one source - how?

Quoting anatoly techtonik techto...@gmail.com: On Fri, Oct 14, 2011 at 2:07 PM, W. Martin Borgert deba...@debian.org wrote: ... The Python thing is to how to generate (and regenerate) these install files? I certainly don't want to create them by hand. I don't know any automated way

Re: Two binary from one source - how?

On 2011-10-13 21:31, anatoly techtonik wrote: There is a long standing bug in trac-bitten [1] to make a spin off a bitten-slave package from the same source that will include just slave client for running builds, which is independent of Trac [2]. Usually, you can build bitten-slave with:

joining the team

Hey Folks, I might just add a packaged titlecase module for New York Manual of Style alike titlecasing. Moreover, I could also contribute to existing packages. my user is: martoss-guest Best wishes Martin -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject

Re: may be a logo?

be your choice among the following 6: http://www.onerussian.com/tmp/pydebian-red_tuned/ I like #6 -- Juan Martin Villanueva Rosario - Argentina

Bug#638720: ITP: openerp6-server -- Enterprise Resource Management (server)

Package: wnpp Severity: wishlist Owner: W. Martin Borgert deba...@debian.org Package name: openerp6-server Version : 6.0.3 Upstream Author : OpenERP supp...@openerp.com URL : http://www.openerp.com/ License : AGPL, GPL, BSD, etc. Programming Lang: Python

Bug#638722: ITP: openerp6-web -- Enterprise Resource Management (web frontend)

Package: wnpp Severity: wishlist Owner: W. Martin Borgert deba...@debian.org Package name: openerp6-web Version : 6.0.3 Upstream Author : OpenERP supp...@openerp.com URL : http://www.openerp.com/ License : OEPL (non-free, but relatively permissive) Programming Lang

Re: Bug#563391: Package Trac 0.12 as well

Quoting Arthur de Jong adej...@debian.org: I've updated the Trac packaging in svn://svn.debian.org/svn/python-apps/packages/trac/trunk to 0.12 and done some migration and cleaning up (see debian/changelog for details). Btw. could you please remove my now unused path

Re: Bug#563391: Package Trac 0.12 as well

Quoting Éric Araujo mer...@netwok.org: Are you sure the full python-setuptools is required, not only python-pkg-resources? Look in debian/changelog :~) I replaced python-setuptools once with python-pkg-resources and had to revert the change. -- To UNSUBSCRIBE, email to

Python utilities package

Hi folks! I am planning to create an ITP for packaging a library of python utilities . It contains several utilities for many kind of applications. Currently is packaged into atheist package but this library is general enough for being used in other projects. It contains classes and structures

Re: Bitten patch to release new version

Quoting Sandro Tosi mo...@debian.org: Talk with the current maintainer (which you're not). In this case it's PAPT. I'm the only Uploader, but happy about anybody helping with Trac and/or Bitten. Currently I'm too busy to help with new versions, but if somebody has time and skills and fun,

Joining python modules / apps packaging team

wishes Martin -- 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/20101114170305.14584oov693kl...@www.schwabenlan.de

Re: dfsg suffix

Quoting anatoly techtonik techto...@gmail.com: Does that mean that I need to figure out why tarball was repacked and manually repack it again with the same changes to do new release? In this case the maintainer (I) was too lazy/sloppy/whatever to document it properly or add a debian/rules

Re: common issue: setlocale handling?

On 2010-08-22 12:38, Julian Andres Klode wrote: Well, it does not really make sense to use invalid locales, so I see no problems if applications exit with a failure. Users should fix their environments instead. It would be nice, if applications would fall back to the C locale and warn about

Re: Packages whith “except” overwriting builtins

Quoting Paul Wise p...@debian.org: Actually, is there any generalised syntax, language, deprecation and mistake checker for python? There are pychecker, pyflakes, and pylint in Debian. This specific case raises a warning in pylint, if I'm not mistaken. -- To UNSUBSCRIBE, email to

Multiple sources/multiple setup.py in one package

Hi, did anyone already put more than one Python source in a Debian package? I.e. more than one setup.py? Do examples exist? TIA! Cheers -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Re: Multiple sources/multiple setup.py in one package

Quoting Piotr Ożarowski pi...@debian.org: [W. Martin Borgert, 2010-06-11] did anyone already put more than one Python source in a Debian package? I.e. more than one setup.py? Do examples exist? TIA! Stefano did, see f.e. python-repoze.who-plugins Perfect, many thanks! (For those who

Django 1.2 for Squeeze?

Hi, would it be realistic/possible to have Django 1.2 in Squeeze? IMHO, it will come too late, because Squeeze will freeze in March and the Django release in planned for March, 9th... But maybe other people are more optimistic? Cheers -- To UNSUBSCRIBE, email to

Trac upgrade documentation (was: jQuery dependency for Trac 0.11)

Quoting anatoly techtonik techto...@gmail.com: That's not sufficient. To update Trac environment you will need to run trac-admin upgrade and optionally trac-admin wiki upgrade. The second point is that web-servers (including Apache) treat symlinks differently and I am unsure how to setup web

Re: jQuery dependency for Trac 0.11 should be 1.3

Quoting anatoly techtonik techto...@gmail.com: Then we should also patch trac-admin deploy command so that it create symlinks to static resources instead of copies to update user environments to latest jQuery automaically. I don't remember, I ever used trac-admin deploy, and I wonder how

Re: jQuery dependency for Trac 0.11 should be 1.3

Quoting anatoly techtonik techto...@gmail.com: If you see jquery.js file inside of its source package - why not to leave it alone - where is the Policy that requires to replace it with some external copy? In general, Debian puts a lot of work into finding and removing embedded code copies.

Re: jQuery dependency for Trac 0.11 should be 1.3

Quoting anatoly techtonik techto...@gmail.com: Then why can't you wait until upstream developers, whose product bundles that library, confirm, validate, test and release fix for that error in their source package together with release announcement? Also in the case of Trac/jQuery. Again, many

Re: jQuery dependency for Trac 0.11 should be 1.3

Quoting anatoly techtonik techto...@gmail.com: Is it possible to create symlink on a symlink? (I am on windows right now - can't test) Yes. That's true. Trac was designed to work even without JavaScript, but Trac plugins are written by community and people often assume that jQuery is

Re: jQuery dependency for Trac 0.11 should be 1.3

Quoting anatoly techtonik techto...@gmail.com: 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 Most Trac plugins do not use JavaScript, even less use jQuery. I don't feel

Re: Unit tests

Quoting anatoly techtonik techto...@gmail.com: Even if most users don't need them, tests greatly increase the value of bugreports and doesn't bloat python packages too much. True. What do other people think of the issue? If unit tests were in the package, reportbug could automatically run

Re: Unit tests

Quoting anatoly techtonik techto...@gmail.com: Python policy is silent about unit tests. Should they be stripped? Or should they be Debianized or left as-is? Just my opinion: Unit tests should be in the source package, but not in the binary package. Most users don't need them, and if somebody

Re: jQuery dependency for Trac 0.11 should be 1.3

Quoting anatoly techtonik techto...@gmail.com: 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

Move GPL discussion elsewhere (was: Python Policy)

Quoting anatoly techtonik techto...@gmail.com: Given that people are tired of discussing things they've already decided for themselves I CC this to debian-legal. Addendum: Given that some Debian documents are released under the terms of the GPL (e.g. our release notes), this discussion has

License entry in egg info files

Hi, I believe that the following entries are incorrect: /usr/share/pyshared/arista-0.9.1.egg-info:License: UNKNOWN /usr/share/pyshared/cups-1.0.egg-info:License: UNKNOWN /usr/share/pyshared/Django-1.1.1.egg-info:License: UNKNOWN /usr/share/pyshared/git_build_package-0.0.0.egg-info:License:

Re: License entry in egg info files

On 2009-10-17 23:59, Ben Finney wrote: So currently I don't think they are bugs of any severity above ‘minor’. I agree, that this is 'minor' or even 'wishlist'. Presumably all these are created by upstream ‘setup.py’ settings, so it would ultimately be for upstream to fix in each case. The

Re: License entry in egg info files

On 2009-10-18 09:46, Ben Finney wrote: I don't have a strong objection in this case, and I can see good arguments for and against a Lintian check. I wouldn't put up a fight either way :-) Me neither, it's certainly one of the least pressing issues we have with Debian Python :~) -- To

Re: Request to join Python Modules Team

if you've read our policy, then yes, you're DPMT member now :-) [1] http://python-modules.alioth.debian.org/python-modules-policy.html Yes, I've read it. Do I need to submit my packages to the subversion repository or do I just keep maintaining them like I have in the past? Thanks, Martin

Request to join Python Modules Team

. Thanks, Martin Kelly -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Request to join Python Modules Team

You can register on alioth even if you're not a DD: your login name will have '-guest' suffix, but that's all. Having an alioth user is a precondition to join any team (so this included). Thanks. I registered and my Alioth login is mkelly-guest. Is that all I need to join? Martn -- To

Backports: Django, web.py, Trac - anyone wants them?

Hi, for some reasons I need lenny backports of python-django, python-webpy and trac. Some of the packages I don't need for production use, but for automatic testing (using bitten) only. I could work with squeeze chroots, but probably I will go for the backports. Now my question: Are more people

Re: trac maintenance activity?

Quoting Andres Salomon dilin...@collabora.co.uk: Ah, just noticed debacle's emails[0] regarding this. You'll certainly find no objections from me. Feel free to take over. Yes, trac will be maintained in the Python Application Packaging Team. I already tried to copy the git history to the

Re: trac maintenance activity?

On 2009-09-11 00:03, anatoly techtonik wrote: There is always Tailor that is capable of converting various repositories into each other. According to the description, tailor supports both git and svn. I may try to do the conversion, just let me know where to get GIT sources (althout HG

Trac - DPMT or PAPT?

Hi, sorry for bringing up this again: Is it OK to put Trac into PAPT, not into DPMT? Reason: I think Trac and at least some of it's plugins should be maintained together (same team, same VCS, Trac users know too well the problem of plugins not fitting in a specific Trac version...), so this is

Re: VCS for Python code

On 2009-08-29 08:46, Michal Čihař wrote: There was recently lengthly discussion about using Git, check archives. The reasons against Hg will be the same + the fact that much poeple do not know it. (I'd be for Git but not for Hg, which I never used before and I'm too lazy to know every VCS

Trac team almost dead?

On 2009-08-26 10:59, Alexander GQ Gerasiov wrote: project on alioth looks nearly dead. We're using trac actively in our lab, so I'll think about entering team to help them a little bit. I wonder, how people feel about moving Trac from its own team to a larger, more active team, i.e. Debian

Re: [Pkg-trac-devel] Trac team almost dead?

On 2009-08-28 12:08, Piotr Ożarowski wrote: question is: are these plugins installed in trac's directory or do they import trac? AFAIK, this depends on the package. Typical plugins are installed into Trac directories, but they have also to import trac to use the APIs. I'm currently not near my

Re: Trac team almost dead?

On 2009-08-28 17:25, Mikhail Gusarov wrote: There are two modes of installation: putting the .egg to the concrete Trac instance and installing it site-wide in the PYTHONPATH. You're probably referring to former. Distribution-friendly way is latter. Than I was wrong. I thought that plugins

Re: Trac team almost dead?

Quoting Christoph Egger deb...@christoph-egger.org: I have some of the trac-plugins ITA/ITPed and would probably consider following trac itself into one of the python Teams. However I wonder how the $VCS will be handled, throwing away trac's git history doesn't sound like a good idea to

Re: [Pkg-trac-devel] Trac team almost dead?

On 2009-08-28 12:21, Piotr Ożarowski wrote: DPMT is fine then (most important ;-) problem solved) Maybe not yet: To me it would make sense to maintain Trac and some Trac plugins in the same team and in the same VCS. DPMT would be OK for Trac, but probably not for all the plugins, that are

python-modules takeover of python-webpy?

Hi, I talked to Kai Hendry, the current maintainer of web.py, who would like to give up the package (python-webpy). I already prepared a new version (current upstream, both open Debian bugs solved), which I would like to upload under the flag of the python-modules-team (my membership is pending).

Re: Bug#486654: adonthell: FTBFS on arm and armel

best to troubleshoot this issue? I suggest you ask on an upstream Python list rather than on debian-python. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bug#486654: adonthell: FTBFS on arm and armel

* Martin Michlmayr [EMAIL PROTECTED] [2008-07-27 15:20]: I suggest you ask on an upstream Python list rather than on debian-python. Anyway, given that 0.3.4.cvs.20050813-3 compiled but 0.3.4.cvs.20050813-4 didn't, I guess this is somehow related to gcc-4.3. -- Martin Michlmayr http

python-central should default to noprepare

that the current approach is error-prone and dirty and I'd like to see it handled better on a Debian system. But I am only I and have been known to err. So? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http

Re: RFS: python-docutils 0.4-6

also sprach Simon McVittie [EMAIL PROTECTED] [2008.03.20.2216 +0100]: Could someone (madduck?) please upload python-docutils (r4865) from python-modules-team svn? It fixes build failure with the current python-central version. Does it address #472046? -- .''`. martin f. krafft [EMAIL

Re: the python editor 'spe' package needs an update.

Steffen Mutter wrote: If SPE keeps on being orphaned I will try to package SPE myself, although it would be nicer if a debian developer wants to adopt SPE. The wnpp bug was renamed to an ITA by Stefano Canepa [EMAIL PROTECTED] - adding him as CC to this mail. What's this

python2.3 removed - open bugs

/binascii.c python2.3-dbg: 334015 334015: minor: python2.3-dbg: missing gdbinit python2.3-dev: 206805 206805: normal: python2.3-dev: pyconfig.h defines _POSIX_C_SOURCE, conflicting with features.h -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED

Re: Bug#381659: konsole: Python console contain reference to non-existing pixmap icon

upload. To summarize: python.desktop lists its icon as python2.3-32.xpm, which doesn't exist. Cheers, Christopher Martin On Sunday 06 August 2006 06:03, Eric Lavarde wrote: Package: konsole Version: 4:3.5.3-2 Severity: minor Hi, /usr/share/apps/konsole/python.desktop refers to /usr/share

Re: multiple pythons and the default

package which just happens to pull in the necessary interpreter... Why? This will give you many unnecessary hard-coded package dependencies. Packages that are reasonably expected to work with this current version and any future version should depend on the default Python. Regards, Martin

Re: when and why did python(-minimal) become essential?

On Fri, Jan 20, 2006 at 11:14:19AM -0800, Matt Zimmerman wrote: If you won't acknowledge that, then know that upstream also object to the name python-base for something which has a stripped-down standard library. Both pythol-minimal and python-base sound to something an end user would expect to

Re: when and why did python(-minimal) become essential?

Martin Michlmayr wrote: I definitely agree we should listen to the Python community, Well, my *personal* view is this: I agree that it is highly desirable that the python package is the entire thing, with all batteries included. I'm uncertain what to think about offering systems that only have

Re: when and why did python(-minimal) become essential?

, no? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: when and why did python(-minimal) become essential?

piss off the python community for making a similar mistake. I definitely agree we should listen to the Python community, especially with the lovely Martin v. Löwis doing so much good work for us. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED

Re: Python .egg support in Debian

for .eggs's. Python developers has benefitted of the quality of Debian for a long time and it would be sad to see it not continue because of disagreement about .egg's. -- Regards, Martin Skøtt Pragmatic Python developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe

Re: [Distutils] formencode as .egg in Debian ??

currently seems to require that the dependencies are provided as plain text in a patch to the upstream sources(*). So the idea certainly is that dependencies are managed by the developer, not automatically. Regards, Martin (*) More precisely, it requires that after unpacking the source

Re: [Distutils] formencode as .egg in Debian ??

() is called. Regards, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [Distutils] formencode as .egg in Debian ??

. Debian developers should work with upstream authors to keep a distutils-based setup.py operational. Regards, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [Distutils] formencode as .egg in Debian ??

\267\r\16\0\0\0\16\0\0..., 132) = 132 So a.zip is read even though the program does not contain a single import statement. What is the untruth I'm spreading? Regards, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [Distutils] formencode as .egg in Debian ??

expect the failure in a typical installation. Regards, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [Distutils] formencode as .egg in Debian ??

this unnecessary, but in a way unfriendly to dpkg (and I assume other Linux package formats). Regards, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [Distutils] formencode as .egg in Debian ??

in a single file. Regards, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: formencode as .egg in Debian ??

for the warning that there are unsupported options). Regards, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Missing setup of /usr/local/lib/python2.4/site-packages

problem. Files are correctly installed under /usr/local, but the .pth files are still missing making the install useless. -- Regards Martin Skøtt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Missing setup of /usr/local/lib/python2.4/site-packages

with the necessary configuration included. Btw. please follow the code of conduct of Debian lists and reply to the list and not to me. See: http://www.debian.org/MailingLists/#codeofconduct -- Regards, Martin Skøtt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe

Re: Python policy proposed changes

python2.1- packages. There are also 125 python2.4- packages, so the majority of the packages has already prepared for the transition. Regards, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Python policy proposed changes

that require such older versions. So when 2.4 becomes the default, only 2.4 (and perhaps 2.5) packages should be built. Regards, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [Pkg-zope-developers] Re: Let's think about removing Python 2.1 and 2.2

. I don't think this will happen (the upgrade path). To me, it sounds best just to remove zope2.6 from etch. There is little point to keep maintaining it as it's really just outdated now. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL

Pills Galore

Never Fill Out Prescription Again, Just Order http://www.ud7.net/ph/coupon/damikatie No longer recieve these messages ud7.netj.php Let not poor Nelly starve.

Re-Fi and save

his Serene Highness He knew Kutuzovs attention would be caught by animal instincts to reawaken they had certain fixed ideas implanted where there are no large quadrupeds have hooked seedssuch hooks as if of Greek thought Indeed the very fact that these men lived in combination they may be

Re: 254795: O: slides -- Python-based Slide Maker

-slides, python2.3-slides, slides-doc, python2.2-slides Description: Python-based Slide Maker See #254795. -- Martin Michlmayr [EMAIL PROTECTED]

where/how to install python libs

to go about creating versions for the different snakes, uh, Pythons? Thanks. Please CC me on replies! -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired

Re: Bug#229370: python2.3: Default site.py breaks stuff

is to fix the buggy applications, i.e. libglade-convert in this case. Regards, Martin

Re: [zope] Zope packaging policy

. If you have patches, please send them to me. I think we should keep this on debian-devel. I do not read debian-python. -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian

Re: [zope] Zope packaging policy

concentrate on getting that which is there finalised. Does anyone know when he's expected to be back? -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have

Re: Summary of python transition problems

; there were two gimp1.2 packages and one got removed. Does testing cope with this? gimp1.2 | 1.2.3-2.4 | testing | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc gimp1.2 |1.2.5-3 | unstable | all -- Martin Michlmayr [EMAIL PROTECTED]

Re: python-stats

here: http://www.nmr.mgh.harvard.edu/Neural_Systems_Group/gary/python.html BTW, this is now orphaned (##212110) in case anyone is interested. -- Martin Michlmayr [EMAIL PROTECTED]

Please remove garchiver

%20Roux Upstream site is dead since 2001-09-27. No new release since 2001-06-27. Gee, one initial upload by Danie (in 2001) and 6 NMUs since then. I will request the package's removal unless someone steps up soon. Plus has a RC bug because of the python-gtk-1.2 migration. -- Martin Michlmayr

Re: garchiver maintainer Danie Roux MIA

-27. Gee, one initial upload by Danie (in 2001) and 6 NMUs since then. I will request the package's removal unless someone steps up soon. -- Martin Michlmayr [EMAIL PROTECTED]

Re: zip archive in python search path

according to the spec. Regards, Martin

Re: Bug#197875: python2.3: module dbm is missing

offer on-disk compatibility of files created by the ndbm over a long period of time. So the module works just fine, except on Linux. Regards, Martin

Re: Documentation generation scripts

it so it works everywheretm. /Martin -- Martin Sjögren [EMAIL PROTECTED] -- [EMAIL PROTECTED] GPG key: http://www.mdstud.chalmers.se/~md9ms/gpg.html let hello = hello : hello in putStr (unlines hello) signature.asc Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel

Re: vpython installation question

On Thu, Apr 03, 2003 at 11:44:49AM -0600, Liudmila Yafremava wrote: it complains that it cannot find module distutils. Why could that be? What should I do to overcome that? Install the python-dev package which contains distutils. -- Martin Skøtt [EMAIL PROTECTED]

<    1   2   3   >