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
signatur
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
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
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
>> s
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
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
> assumi
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
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-
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 l
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 libra
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=$P
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 vers
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
>
> Ho
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
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
--
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 Pe
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 remov
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,
p
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
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
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.
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
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,
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
> infecte
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 f
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 a
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
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 fo
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 pyf
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
ink
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/
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
> b
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/ch
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
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 "unsubsc
> 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,
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
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
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 respon
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.de
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:
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. Wh
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 SC
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
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 b
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 upst
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?
>
>
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
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
> upstr
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 refer
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 k
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 O
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
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 provi
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
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
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
actuall
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
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 resolu
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
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), vario
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 (sha
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.debia
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 d
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
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 Py
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
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.
Upstre
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 d
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/Pa
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:/
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 upstrea
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
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 look
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
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 debi
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
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,
> b
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
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
vendorise
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 vendore
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 i
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-chan
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 s
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
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.
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
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...@lis
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 UNSUBSCRIB
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/f
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.
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 an
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
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
> infrastructu
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 bundle
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 devel
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:/
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
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, dete
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
1 - 100 of 223 matches
Mail list logo
