Steve Holden writes:
> Hey, isn't Ubuntu Debian-based? ...
Ouch. I don't actually use Ubuntu, but when everybody on my local LUG
list from the "Linux should be Windows but cheaper" newbies to former
NetBSD developers is grouching about upgrade hell, I don't see any
real benefits to be gained.
On 4/01/2009 9:29 PM, Ulrich Eckhardt wrote:
If I'm still misunderstanding, can you be more specific about the exact
problem (ie, the exact function you are referring to, and how you intend
calling it)?
trunk/_fileio.c/fileio_init()
Let's leave aside that you can also pass a filedescriptor, th
2009/1/4 Brett Cannon :
> Bazaar has been backwards-compatible with everything from my
> understanding, so any changes they have made to the repository layout
> or network protocol they use should not be an issue regardless of what
> client or server versions are being used. As for the version numb
Aahz writes:
> all. Because I was lazy, last weekend I finally did a two-stage upgrade
> from 7.10 to 8.04 and then 8.10, with zero noticeable problems.
The scary one is two independent reports of fstab corruption in the
8.04 to 8.10 upgrade. It is claimed to be unfixable by booting from
CD,
[sorry, dropped one pair of mails off the list, hence also the overquoting]
On Sunday 04 January 2009 01:07:08 Mark Hammond wrote:
> > > On 'normal' windows you generally would need to use
> > > WideCharToMultiByte() to get a 'char *' version of your wchar
> > > string but I expect you already kno
>> CC=icc ./configure --prefix=$HOME/tmp/icc-python
>>
>> That failed computing the size of size_t because it tries to incorrectly
link
>> with -lgcc_s.
Martin> Can you provide the relevant section of config.log? What is the
Martin> precise command that configure is invo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 4, 2009, at 11:26 AM, Stephen J. Turnbull wrote:
Aahz writes:
all. Because I was lazy, last weekend I finally did a two-stage
upgrade
from 7.10 to 8.04 and then 8.10, with zero noticeable problems.
The scary one is two independent repo
>> ...
>> configure:10332: checking size of size_t
>> configure:10637: icc -o conftest -g -O2 conftest.c >&5
>> ld: library not found for -lgcc_s
Martin> I think you have the source of the problem right there: your icc
Martin> installation is broken. It is unable to buil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 4, 2009, at 4:21 AM, Stephen J. Turnbull wrote:
Steve Holden writes:
Hey, isn't Ubuntu Debian-based? ...
Ouch. I don't actually use Ubuntu, but when everybody on my local LUG
list from the "Linux should be Windows but cheaper" newbies to
I missed the beginning here; oh well.
On Sun, Jan 4, 2009 at 9:51 AM, Aahz wrote:
> On Sun, Jan 04, 2009, Stephen J. Turnbull wrote:
>> Steve Holden writes:
>>>
>>> Hey, isn't Ubuntu Debian-based? ...
>>
>> Ouch. I don't actually use Ubuntu, but when everybody on my local LUG
>> list from the "L
On Sun, Jan 4, 2009 at 12:05 PM, wrote:
> Hmmm, OK... Why do we need two ways to spell "don't use gcc"?
Think of it like the two keys to the atom bomb. :-P
--
Cheers,
Leif
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mail
I downloaded an evaluation copy of the Intel compiler for Mac and tried (so
far unsuccessfully) to configure with it. I have tried:
CC=icc ./configure --prefix=$HOME/tmp/icc-python
That failed computing the size of size_t because it tries to incorrectly link
with -lgcc_s.
Then I tried forc
> CC=icc ./configure --prefix=$HOME/tmp/icc-python
>
> That failed computing the size of size_t because it tries to incorrectly link
> with -lgcc_s.
Can you provide the relevant section of config.log? What is the precise
command that configure is invoking, and what is the precise error
messag
>> ...
>> configure:10332: checking size of size_t
>> configure:10637: icc -o conftest -g -O2 conftest.c >&5
>> ld: library not found for -lgcc_s
Martin> I think you have the source of the problem right there: your icc
Martin> installation is broken. It is unable to buil
> ...
> configure:10332: checking size of size_t
> configure:10637: icc -o conftest -g -O2 conftest.c >&5
> ld: library not found for -lgcc_s
I think you have the source of the problem right there: your icc
installation is broken. It is unable to build even trivial programs.
To
Stephen J. Turnbull wrote:
> And for that ML this is huge; I don't recall so many screams on a
> commercial vendor upgrade since Red Hat went from HJ Liu libc to glibc
> 2.
I've had problems with Kubuntu's graphical updater crashing, but never
anything a "sudo apt-get dist-upgrade" didn't fix.
Al
On Sun, Jan 04, 2009, Stephen J. Turnbull wrote:
> Steve Holden writes:
>>
>> Hey, isn't Ubuntu Debian-based? ...
>
> Ouch. I don't actually use Ubuntu, but when everybody on my local LUG
> list from the "Linux should be Windows but cheaper" newbies to former
> NetBSD developers is grouching ab
Martin v. Löwis schrieb:
>> ...
>> configure:10332: checking size of size_t
>> configure:10637: icc -o conftest -g -O2 conftest.c >&5
>> ld: library not found for -lgcc_s
>
> I think you have the source of the problem right there: your icc
> installation is broken. It is unable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 3, 2009, at 11:29 PM, Steve Holden wrote:
Brett Cannon wrote:
[...]
I have been using bzr for all of my importlib work. It's worked out
well sans the problem that SOMEONE Barry has not
upgraded the bzr installation to support the newest wire
Disclaimer: I'm a member of the team working with Brett on the DVCS
PEP, and definitely pro-DVCS (specifically working on the git parts).
"Martin v. Löwis" writes:
> If "switching to a modern DVCS" means that users now need to start
> compiling their VCS before they can check out Python,
It do
Mark Hammond schrieb:
> Would it be practical and desirable to handle this situation more
> gracefully, possibly just leaving sys.std* set to None and letting
> whatever exceptions then occur happen as normal without terminating the
> process? Given it is an edge-case, I thought I'd open it here f
Martin v. Löwis v.loewis.de> writes:
>
> Correct. To specify a different compiler, set the CC environment
> variable, and don't pass the --without-gcc flag.
Perhaps --without-gcc should be removed, if it's both useless and misleading?
(note: I don't have an interest in the matter)
___
> This code looks suspicious:
>
> if test ${cur_target} '>' 10.2; then
> cur_target=10.3
> fi
>
> If I comment it out configure succeeds. This code dates from r65061
No, it dates from r45800:
r45800 | ronald.oussoren | 2006-04-29 13:31:35 +0200 (Sa,
> Perhaps --without-gcc should be removed, if it's both useless and misleading?
> (note: I don't have an interest in the matter)
I had the same thought.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
Since print is now a builtin function why is there still a PRINT_EXPR
opcode?
Skip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archiv
> Isn't the latter supposed to point to the py3k branch buildbots?
Thanks for pointing that out - it is fixed now.
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.pyth
On Sun, Jan 4, 2009 at 5:28 PM, wrote:
> Since print is now a builtin function why is there still a PRINT_EXPR
> opcode?
I believe it's used in the interactive interpreter to display the repr
of an expression.
--
Regards,
Benjamin
___
Python-Dev ma
>> Since print is now a builtin function why is there still a PRINT_EXPR
>> opcode?
Benjamin> I believe it's used in the interactive interpreter to display
Benjamin> the repr of an expression.
Wouldn't it make more sense for the interactive interpreter to call
print(repr(exp
On Sun, Jan 4, 2009 at 5:36 PM, wrote:
>
>>> Since print is now a builtin function why is there still a PRINT_EXPR
>>> opcode?
>
>Benjamin> I believe it's used in the interactive interpreter to display
>Benjamin> the repr of an expression.
>
> Wouldn't it make more sense for the i
Barry Warsaw wrote:
> On Jan 3, 2009, at 11:29 PM, Steve Holden wrote:
>
>> Brett Cannon wrote:
>> [...]
>>> I have been using bzr for all of my importlib work. It's worked out
>>> well sans the problem that SOMEONE Barry has not
>>> upgraded the bzr installation to support the newest wire protoco
Stephen J. Turnbull wrote:
> Aahz writes:
>
> > all. Because I was lazy, last weekend I finally did a two-stage upgrade
> > from 7.10 to 8.04 and then 8.10, with zero noticeable problems.
>
> The scary one is two independent reports of fstab corruption in the
> 8.04 to 8.10 upgrade. It is cla
s...@pobox.com writes:
> >> That failed because of a bug in configure.in:
> >>
> >> case $withval in
> >> no) CC=cc
> >> without_gcc=yes;;
> >> yes)CC=gcc
> >> without_gcc=no;;
> >> *) CC=$withval
> >> without_gcc=$withval;;
> >>
>
Barry Warsaw writes:
> > The scary one is two independent reports of fstab corruption in the
> > 8.04 to 8.10 upgrade. It is claimed to be unfixable by booting from
> > CD, mounting the partition, and editing fstab: the editor saves but
> > the fstab returns to the original corrupt state upon
On Sun, Jan 4, 2009 at 8:51 PM, Steve Holden wrote:
> Ubuntu is a victim of its own success. They now have to deal with the
> same diversity of hardware environments as Windows. I hope that
> Canonical will find a way to stabilize things.
I think it's actually worse. Microsoft can always (and, i
34 matches
Mail list logo
