On 26 October 2012 14:20, Paul Tagliamonte wrote:
> On Fri, Oct 26, 2012 at 11:03:34AM +0100, Thomas Kluyver wrote:
>> On 26 October 2012 09:19, Floris Bruynooghe wrote:
>> > Several people have said they don't think this is a good idea. But
>> > why not? Th
On 25 October 2012 20:34, Piotr Ożarowski wrote:
> [Steve Langasek, 2012-10-25]
>> On Thu, Oct 25, 2012 at 10:56:05AM -0400, Barry Warsaw wrote:
>> > Using -E fixed the immediate bug, but I think it is generally useful to
>> > include -s also, so as to avoid any potential breakage of system script
Hi,
On 4 April 2012 15:47, Simon Chopin wrote:
> IMHO there is three alternatives:
> * Provide the scripts for all Python versions available, py.test[-3]
> pointing to the default Python version. It would mean that the
> package would depend on python-all and python3-all because of the
>
On 22 April 2011 19:55, Stefano Rivera wrote:
> Hi Barry (2011.04.22_03:28:12_+0200)
>> When I click on 'last log' for say ia64, I just see a build log with
>> no failures in it. So why does it show up on the main page with
>> straight red-X's?
>
> The transition tracker is just tracking the stat
Hi
The wiki page at http://wiki.debian.org/Python/PyCentral2DhPython2
tells you to remove the XB-Python-Version lines in debian/control but
the python policy still says they are required in section 2.3. I
presume this is outdated in the policy? If so any reason why this
isn't updated?
Regards
F
On 28 November 2010 00:18, Jakub Wilk wrote:
> * Floris Bruynooghe , 2010-11-28, 00:06:
>>
>> So now that these have been filed, is there a consensus on what to do
>> if only documentation is affected?
>
> How about, well, fixing it? :) It's not like correcting d
[Sandro: sorry for the mistaken private reply]
On 27 November 2010 22:50, Sandro Tosi wrote:
> On Mon, Nov 22, 2010 at 14:50, Jakub Wilk wrote:
>> * Sandro Tosi , 2010-11-17, 23:37:
Any volunteers to file bugs? :)
>>>
>>> I'll do that tomorrow, if no-one beats me.
>>
>> Any news on tha
On Sun, Aug 22, 2010 at 02:16:21PM +0200, Vincent Bernat wrote:
> OoO En cette matinée ensoleillée du dimanche 22 août 2010, vers 09:44,
> Paul Wise disait :
>
> >> 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
On Fri, Jul 16, 2010 at 10:03:24AM +1000, Brian May wrote:
> At present our (planned but not implemented) approach is to have our
> python dist-utils script create a directory karaage/conf under the
> python path, and then karaage can import then using "import
> karaage.conf.settings" for example.
On Mon, Apr 26, 2010 at 09:44:52AM +0200, Josselin Mouette wrote:
> Le dimanche 25 avril 2010 à 19:37 +0100, Floris Bruynooghe a écrit :
> > You could try setting RUNPATH/RPATH into the extension module. If
> > it's using distutils you can use --rpath to setup.py build_ext, s
Hi
On Sun, Apr 25, 2010 at 02:10:12PM +0200, Sylvestre Ledru wrote:
> * All Scilab libraries are stored in /usr/lib/scilab/
>
> * cdll.LoadLibrary("/usr/lib/scilab/libscilab.so") will fails
> since /usr/lib/scilab is not in the search path for libraries
>
> * setting thhe LD_LIBRARY_PATH into Py
On Fri, Jan 15, 2010 at 02:16:10PM +1100, Ben Finney wrote:
> Cyril Brulebois writes:
>
> > Ben Finney (15/01/2010):
> > > Now, this is a “pedantic”-level tag, but it does seem valid: the
> > > SOURCES.txt file is in fact modified from the original upstream
> > > source.
> >
> > Just rm it in cl
On Wed, Nov 18, 2009 at 04:03:32PM +0100, Josselin Mouette wrote:
> Le mercredi 18 novembre 2009 à 10:02 +0100, Wolodja Wentland a écrit :
> > PEP 345 [1] describes version 1.2 of the PKG-INFO file that will be
> > shipped with Python distributions in the future.
>
> > Requires-External: C
> > Re
On Thu, Nov 05, 2009 at 10:21:25AM +1100, Graeme Cross wrote:
> I thnk that Roberto was asking about Python(x,y) rather than version x.y
> of a standard Python install.
>
> Python(x,y) is a package of Python plus various tools and libraries for
> science and engineering:
>
> http://www.pythonxy
On Wed, Nov 04, 2009 at 10:12:52PM +0100, roberto wrote:
> hello
> i need to install python(xy) in debian 5.0;
> which is the best way to do it ?
> compile it from source ?
> is it possible to install the related ubuntu package ?
"apt-get install python"
or
"apt-get install pythonX.Y" where "X.
On Mon, Sep 21, 2009 at 12:35:19AM +0200, Wolodja Wentland wrote:
> On Sun, Sep 20, 2009 at 22:18 +0200, Bernd Zeimetz wrote:
> > Wolodja Wentland wrote:
>
> [ placed on top because this is the main point ]
>
> > > If however the *env python scheme is enforced in the policy the problems
> > > I o
On Tue, Sep 08, 2009 at 01:49:06AM +0700, Mikhail Gusarov wrote:
>
> Twas brillig at 11:37:50 07.09.2009 UTC-07 when vor...@debian.org did gyre
> and gimble:
>
> SL> They were part of the design that came out of the python packaging
> SL> BoF in DebConf 6 that you then proceeded to ignore enti
On Tue, Feb 03, 2009 at 09:18:31AM -0500, Guy Hulbert wrote:
> On Tue, 2009-03-02 at 09:06 -0500, Yaroslav Halchenko wrote:
> > Unfortunately I can't find clear description of the 'staff' group
> > destiny
> > nowhere in Debian documentation
>
> Fortunately, I just spent 20-30 minutes going throu
On Tue, May 20, 2008 at 01:41:20PM +0200, Josselin Mouette wrote:
> Le lundi 19 mai 2008 à 19:22 +0100, Floris Bruynooghe a écrit :
> > > The latter approach is less fragile overall,
> >
> > How is that? As far as I can see both python-central and
> > python-support
Hello
On Mon, May 19, 2008 at 12:49:11PM +0200, Josselin Mouette wrote:
> Le dimanche 18 mai 2008 à 11:35 -0700, Monty Taylor a écrit :
> > 1. What are the real differences between these two?
>
> Technically speaking, they use very different approaches. Python-central
> links modules at their ori
On Tue, Mar 11, 2008 at 08:43:06AM +0100, Matthias Klose wrote:
> Currently Debian's python has /usr/local/lib/python2.x/site-packages
> in sys.path allowing for installation of local modules. Barry did
> point out that this conflicts with a python installation, where
> /usr/local is the default p
On Tue, Mar 11, 2008 at 09:45:21AM -0400, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mar 11, 2008, at 3:43 AM, Matthias Klose wrote:
>
>> Currently Debian's python has /usr/local/lib/python2.x/site-packages
>> in sys.path allowing for installation of local modules.
Hello Ondrej
On Sat, Feb 09, 2008 at 12:01:52AM +0100, Ondrej Certik wrote:
> the python-profile is in non-free, so what free tool do you use for
> profiling your python programs? There is cProfile in python2.5, which
> seems to be free, but for showing
> the result I need pstat, which is again no
Hello
The email in [1] discusses the long double transition from 64 to 128
bit. It claims that the python2.[45]-dev packages need to be updated
for this too, however I can not find the related bug reports for this.
I have also looked in de changelog files but can't seem to find a
mention of it.
Hi
On Wed, Mar 28, 2007 at 08:39:42PM +0200, Pierre Habouzit wrote:
> wrt the "current" thingie, I may have a proposal ready soon, I just
> need to polish the details, and look how "hard" it would be to upgrade
> the dh_py* tools to them. Well, I've a hard week of paid work ahead, so
> I don't e
On Sat, Feb 24, 2007 at 06:17:35PM -0800, Suhas kurse wrote:
> I am new to Python programming.
>
> I want to set the PYTHONPATH in "Windows XP". How should I go about it
This is the wrong place for that question. Have a look at
http://www.python.org/community/lists for where to ask your q
On Mon, Sep 04, 2006 at 09:16:59AM +0200, Raphael Hertzog wrote:
> On Mon, 04 Sep 2006, Steve Langasek wrote:
> > > Pyversions is mainly used at build-time and not at installation time.
> > > Whatever requires pyversions (and in this case python-gnome2) should be
> > > depending on the first versio
On Mon, Aug 28, 2006 at 09:53:20AM +0200, Josselin Mouette wrote:
> Le dimanche 27 août 2006 à 23:33 -0700, Steve Langasek a écrit :
> > the questions of their utility likewise seems
> > to have only been raised in private. I think you have tried to kill off
> > these fields because you personally
On Sat, Aug 26, 2006 at 11:18:15AM +0200, Josselin Mouette wrote:
> Le vendredi 25 août 2006 à 17:09 -0700, Steve Langasek a écrit :
> > > As long as these fields don't even have clear semantics, implementing
> > > them is, at best, useless.
> >
> > So, why has there been no discussion about the p
Hello
I've somewhat lost track of the exact current status of the new
policy.
AIUI debian/pycompat is not needed anymore currently as dh_python has
enough by having the XS-Python-Version field, while if you are using
python-support dh_python is not used at all anymore so it doesn't need
the debia
On Tue, Aug 22, 2006 at 01:00:45AM +0200, Josselin Mouette wrote:
> Le mercredi 16 août 2006 à 16:21 +0200, Raphael Hertzog a écrit :
> > As I can understand him, we really should respect his wish. If Matthias
> > agrees,
> > I can extract the "dependency" generation code from dh_python and create
On Tue, Jun 20, 2006 at 01:34:35AM +0200, Raphael Hertzog wrote:
> On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > - uses "XS-Python-Standards-Version: 0.4" as reference field to run in new
> >policy mode. The presence of XS-Python-Version will also trigger the new
> >policy mode (this is
On Mon, Jun 19, 2006 at 09:07:00PM +0200, Raphael Hertzog wrote:
> BTW, the syntax of the Python-Version field comes directly from
> python-central and it has not been discussed if the current syntax is the
> best needed to achieve the second point.
This is a valid point. But if it is found to b
On Mon, Jun 19, 2006 at 12:31:25PM -0500, Joe Wreschnig wrote:
> On Mon, 2006-06-19 at 19:24 +0200, Raphael Hertzog wrote:
> > Hello,
> >
> > as you may have read in the previous mail, the latest dh_python uses
> > a "debian/pyversions" file to find out the Python versions that the
> > packages su
On Mon, Jun 19, 2006 at 04:13:52PM +0900, Kai Hendry wrote:
> I am a little wary of the new lintian error rule to build depend on
> python-all-dev|python-dev|python
>
> What should I be using in my package's case? Could someone clarify. I
> have read the new policy, though perhaps I missed somethi
Hi
I have been packaging VPython for some time now and would like to get
it into the main Debian archive. There has been an ITP for this way
back in September 2001 (#112118) which was retitled to RFP in December
2002 due to nothing happening with it. According the the WNPP bug
(#112118) Debian J
Hello
I was wondering why there is still no way to produce these single
packages for all versions (see policy 2.2.3 (2.)). Is there anything
holding back the scripts in pythonX.Y to support this?
Currently all packages have to be reuploaded before a new pythonX.Y
package can progress. This seem
37 matches
Mail list logo
