wahjava...@gmail.com (Ashish SHUKLA) writes:
> Steve Holmes writes:
>> On Fri, Sep 17, 2010 at 05:02:24AM +0530, Ashish SHUKLA wrote:
>>> Steve Holmes writes:
>>> > Do I have to set up anything in advance in order to use ispell in
>>> > emacs with the aspell program? See the message below for the
On 21/10/10 01:45, maxc wrote:
There is an excellent post by Guido here, Hilton:
http://mail.python.org/pipermail/python-3000/2008-February/011910.html
That was in February 2008... Back when we were using python-2.5 because
neither python-2.6 or python-3.0 had been released. So I doubt even
On 10/20/2010 06:52 AM, Hilton Medeiros wrote:
HackerNews, Slashdot, ...:
- Someone post an announcement with 10 lines;
- They read it (or not) and think that that is all the information
behind the story;
- They furiously start typing the first thing that pops in their mind;
Often preceded
On Wed, Oct 20, 2010 at 3:00 PM, wrote:
> On Wed, Oct 20, 2010 at 12:10:03PM -0500, C Anthony Risinger wrote:
>
>> the point is that it really, really, really... doesn't matter what
>> `python` is symlinked to. developers need to have the competence to
>> instruct the system appropriately, and c
On Wed, Oct 20, 2010 at 12:10:03PM -0500, C Anthony Risinger wrote:
> the point is that it really, really, really... doesn't matter what
> `python` is symlinked to. developers need to have the competence to
> instruct the system appropriately, and construct the environment they
> need to function
On Wed, Oct 20, 2010 at 10:52 PM, Dan McGee wrote:
> On Wed, Oct 20, 2010 at 2:43 PM, Evangelos Foutras
> wrote:
>> What do we do for stuff like PHP which will get linked to PostgreSQL
>> 9.0.1 which is in [testing] right now? Or will PostgreSQL be moved out
>> of [testing] at the same time as t
On Wed, Oct 20, 2010 at 2:43 PM, Evangelos Foutras wrote:
> On Tue, Oct 19, 2010 at 7:58 AM, Allan McRae wrote:
>> Hi,
>>
>> Time to move on to the next rebuild! This time it is for db-5.1.
>>
>> There are the following soname changes:
>> libdb-4.8.so -> libdb-5.1.so
>> libdb-4.so -> libdb-5.s
On Tue, Oct 19, 2010 at 7:58 AM, Allan McRae wrote:
> Hi,
>
> Time to move on to the next rebuild! This time it is for db-5.1.
>
> There are the following soname changes:
> libdb-4.8.so -> libdb-5.1.so
> libdb-4.so -> libdb-5.so
> libdb_cxx-4.8.so -> libdb_cxx-5.1.so
> libdb_cxx-4.so -> libdb
Le 20/10/2010 21:00, solsTiCe d'Hiver a écrit :
Le mardi 19 octobre 2010 à 18:54 +0200, Clément Démoulins a écrit :
And the dependencies must be updated from python to python2.
also I guess something like python>2.6.5 should become python2>2.6.5
which does not make any sense since python2 in
On Oct 20, 2010, at 01:10 PM, C Anthony Risinger wrote:
On Wed, Oct 20, 2010 at 10:45 AM, maxc wrote:
>
> There is an excellent post by Guido here, Hilton:
> http://mail.python.org/pipermail/python-3000/2008-February/011910.html
>
> Guido seems to favor using /usr/bin/python3.0 or /usr/bin/p
Le mardi 19 octobre 2010 à 18:54 +0200, Clément Démoulins a écrit :
>
> And the dependencies must be updated from python to python2.
>
also I guess something like python>2.6.5 should become python2>2.6.5
which does not make any sense since python2 in archlinux is >= 2.7
and then could be shortene
On Wed, Oct 20, 2010 at 01:26:26PM -0400, David Rosenstrauch wrote:
> So, it's helpful to know that one of the message buses is the source
> of the issue. Do you know if there's any way to narrow it down more
> than that? i.e., find out which config file is causing this?
It's caused by the avahi
On 10/20/2010 01:08 PM, Aljosha Papsch wrote:
It means, D-BUS (or any message bus) is missing a group specified in its
configuration file. A solution might be to just create the group.
No, I'm not going to go and blindly create the group. I want to
understand what in my configuration is expe
On Wed, Oct 20, 2010 at 10:45 AM, maxc wrote:
>
> There is an excellent post by Guido here, Hilton:
> http://mail.python.org/pipermail/python-3000/2008-February/011910.html
>
> Guido seems to favor using /usr/bin/python3.0 or /usr/bin/python3 and
> /usr/bin/python as symlinks to the respective ver
It means, D-BUS (or any message bus) is missing a group specified in its
configuration file. A solution might be to just create the group.
On 11:17 Wed 20 Oct , Dan McGee wrote:
> Fucking hell! Can we stop with this constant nagging on the list? It
> doesn't help (as you can see), you waste 1926 people's time with the
> message (yes, this list has this many subscribers, and it is soon to
> be one less), and it just doesn't need to be
Am Wed, 20 Oct 2010 12:02:27 -0400
schrieb Matthew Gyurgyik :
> Really please, please don't top post.
> http://www.river.com/users/share/etiquette/
And, really please, only quote the relevant parts to which the answer
refers.
Heiko
On Wed, Oct 20, 2010 at 11:02 AM, Matthew Gyurgyik wrote:
> On 10/20/2010 11:45 AM, maxc wrote:
>>
>> There is an excellent post by Guido here, Hilton:
>> http://mail.python.org/pipermail/python-3000/2008-February/011910.html
>>
>> Guido seems to favor using /usr/bin/python3.0 or /usr/bin/python3
On 10/20/2010 11:45 AM, maxc wrote:
There is an excellent post by Guido here, Hilton:
http://mail.python.org/pipermail/python-3000/2008-February/011910.html
Guido seems to favor using /usr/bin/python3.0 or /usr/bin/python3 and
/usr/bin/python as symlinks to the respective versions of Python.
Been seeing a strange message recently on boot. Seems to have only
appeared in the last few weeks.
'Unknown group "netdev" in message bus configuration file'
Anyone know what's causing it and/or how to get rid of it?
Thanks,
DR
There is an excellent post by Guido here, Hilton:
http://mail.python.org/pipermail/python-3000/2008-February/011910.html
Guido seems to favor using /usr/bin/python3.0 or /usr/bin/python3 and
/usr/bin/python as symlinks to the respective versions of Python.
'Perhaps we should only install "pyth
On Wed, 20 Oct 2010 10:58:42 -0400
Max Countryman wrote:
> That is fine unless the Python development team has decide that
> python3 will not become python.
>
> Python 2.7.x will be maintained for quite some time. (In excess of
> four more years.) Even after it is dropped in the future there's
On Wed, Oct 20, 2010 at 11:16, Armando M. Baratti
wrote:
> Em 20-10-2010 05:24, Stefano Z. escreveu:
>>
>> anyone know if reportlab does work with python3 ?
>>
>
> No, reportlab doesn't work with python3.
> Neither Django, nor Twisted.
>
> As well the modules below are incompatible with python3 (t
Em 20-10-2010 05:24, Stefano Z. escreveu:
anyone know if reportlab does work with python3 ?
No, reportlab doesn't work with python3.
Neither Django, nor Twisted.
As well the modules below are incompatible with python3 (to mention a few):
- PyGTK2
- Pyjamas
- Kiwi
- Beaker
- Cheetah
- CherryPy
On 10/20/2010 10:58 AM, Max Countryman wrote:
That is fine unless the Python development team has decide that python3 will
not become python.
Python 2.7.x will be maintained for quite some time. (In excess of four more
years.) Even after it is dropped in the future there's no indication that
That is fine unless the Python development team has decide that python3 will
not become python.
Python 2.7.x will be maintained for quite some time. (In excess of four more
years.) Even after it is dropped in the future there's no indication that the
python3 binary is intended to become the py
On Wed, Oct 20, 2010 at 9:14 AM, Max Countryman wrote:
>
> But is that what Python development has decided?
I'm not sure what they have recommended. Ultimately it's up to the
distros to decide such things; I have seen that written more then once
by BFDL and friends.
I think what Arch is doing i
But is that what Python development has decided?
On Oct 20, 2010, at 10:05, C Anthony Risinger wrote:
> On Wed, Oct 20, 2010 at 9:03 AM, C Anthony Risinger wrote:
>>
>> i like the python2.7, python2, python3.1, python3, etc, scheme... i
>> think this makes it very easy for developers to select
On Wed, Oct 20, 2010 at 9:03 AM, C Anthony Risinger wrote:
>
> i like the python2.7, python2, python3.1, python3, etc, scheme... i
> think this makes it very easy for developers to select the specific
> interpreter they need, if any. i hope this trend becomes/is defacto.
> if you are just running
On Wed, Oct 20, 2010 at 8:52 AM, Hilton Medeiros
wrote:
> On Wed, 20 Oct 2010 04:31:17 + (UTC)
> Mithrandir wrote:
>
>> Max Countryman me.com> writes:
>>
>> >
>> > > I failed to find a reference, but I seem to remember the Python
>> > > team
>> deciding at some point that they
>> > intended
I think that my only concern at this point is how the Python development team
sees the future of the binary: if the python and python3 convention is kept I
worry about the ease of portability apropos to development under Arch.
For further in-depth discussion of the overall move the comments of t
On Wed, 20 Oct 2010 04:31:17 + (UTC)
Mithrandir wrote:
> Max Countryman me.com> writes:
>
> >
> > > I failed to find a reference, but I seem to remember the Python
> > > team
> deciding at some point that they
> > intended to keep the name "python" for the Python 2.X binaries
> > perpetual
Am Thu, 14 Oct 2010 14:19:26 +0300
schrieb Ionuț Bîru :
> somebody already uploaded a new build, libreoffice-new. the name is
> kinda stupid and it makes me want to delete it.
I'd second this. It also seems to be a duplicate to libreoffice-bin.
And libreoffice-build should be deleted, too, renam
> Those are AUR packages, you need to ask their maintainers in the AUR to
> make the necessary changes.
Learn2read, please. I was given the impression that this was going to
be solved with the python package:
On Thu, Oct 7, 2010 at 1:49 PM, Allan McRae wrote:
>Hmm... I probably should have adde
Oh is there another thread on this list? My apologies if so! I just joined
earlier yesterday. :)
On Oct 20, 2010, at 12:31 AM, Mithrandir wrote:
> Ha ha! We posted at virtually the same time! (Or not...) :D
On 20-10-2010 05:35, Angus wrote:
>>> Hmm... I probably should have added a version to the provides line in the
>>> python package. Currently it only provides "python3" and not a version so
>>> the versioned deps in those AUR packages are causing issues. I'll get
>>> around to that before this
Max Countryman me.com> writes:
>
> > I failed to find a reference, but I seem to remember the Python team
deciding at some point that they
> intended to keep the name "python" for the Python 2.X binaries perpetually,
and require Python 3.X to be
> invoked as "python3". Arch might be alone in mak
anyone know if reportlab does work with python3 ?
38 matches
Mail list logo
