[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

[Gregory P. Smith]

Gregory P. Smith <[EMAIL PROTECTED]> added the comment:

instrumenting Python/thread_pthread.h and turning on thread debugging in
Python/thread.c, FreeBSD raises the Fatal error within pthread_create().

I'm inclined to say that this is a FreeBSD 6.3 bug.  The
fbsd_thr_crash.py test case is a good way to reproduce the problem.  I'd
imagine a similar bit of C code could be written.

What should we do in Python for this?  Just disable this unit test on
FreeBSD?

--
priority: high -> normal

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

[Gregory P. Smith]

Gregory P. Smith <[EMAIL PROTECTED]> added the comment:

attaching a stand alone script to exercise the bug.  based on the
prints, the error appears to happen during the t.start() call to launch
the joiningfunc() thread from the child processes worker thread (its the
main/only thread in the child process so far).

Added file: http://bugs.python.org/file11492/fbsd_thr_crash.py

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

[Gregory P. Smith]

Gregory P. Smith <[EMAIL PROTECTED]> added the comment:

and as expected, also happens with py3k.

--
versions: +Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3871] cross building python for mingw32 with distutils

[Roumen Petrov]

Roumen Petrov <[EMAIL PROTECTED]> added the comment:

P.S.: this patch cover changes in the python C-code proposed in issue
1412448 as include only necessary modifications.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3870] Parser/asdl_c.py requires python in order to build python

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Yes, that's why what it builds is included in the svn repo by default.
You can avoid the build problems by touching Include/Python-ast.h and
Python/Python-ast.c.

--
nosy: +benjamin.peterson
resolution:  -> invalid
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3871] cross building python for mingw32 with distutils

[Roumen Petrov]

New submission from Roumen Petrov <[EMAIL PROTECTED]>:

This is a completely new patch against trunk that try to resolve mingw32
build. The first version to show problems with current python builds
system, to propose solutions/work-arounds and to be stating point for
discussion. Also I prefer some issues to be resolved later when we agree
on the basic issues.

The patch is tested in cross-compilation environment and native build
has to be tested too. Also the patch show how to use cross-compilation
environment and require patch posted in
issue 3754 ("minimal cross-compilation support for configure") to be
applied first.

The new patch share many commons with issue 841454 "Cross building
python for mingw32" posted by Andreas Ames, on 2003-11-13), but build
process use distutils instead scons.
Also some mingw related changes from issue 1597850 ("Cross compiling
patches for MINGW" - Han-Wen Nienhuys, from 2006-11-16) are shared too,
but we differ in concept how to use cross-compilation environment.
The correct way is to use $host variable (see issue 3754).

Also my patch use python installed on build system along with some hacks
to overcome distutils limitations.

The main issue "how to select correct compiler" in cross-compilation
environment isn't resolved at all. The patch is tested with installed
python version 2.4. 
Usually the cross-compiler is installed in same directories as native
compiler but tools are prefixed by -- (see meanign of "host
triplet"). In this environment we can't cross-compile even if we select
mingw as compiler in arguments for "setup.py":
The method get_versions() from cygwinccompiler.py call find_executable
for to find gcc, ld, dllwrap but on build system they point to native
compiler and that aren't prefixed. Also the expression "result =
re.search('(\d+\.\d+(\.\d+)*)',out_string)" return as example
'2.17.50.0.6' and later StrictVersion fail since value is not in format
N.N{.N{A{N}}}. If we replace '*' with '?" in regular expression we will
get correct  result, but this isn't right solution.
So the question is 'how to pass compiler to distutils' (as example for
python 2.4) remain open.

Work-around: install mingw cross-suite in own directory (MINGW_ROOT) and
prepend PATH environment variable with both paths:
- $MINGW_ROOT/bin
- $MINGW_ROOT//bin where  is something like
i586-pc-mingw32 (depend from you host selected when you build suite).
In this case find_executable will find mingw ld and since -v option
return something like "GNU ld version 2.17.50 20060824", regular
expresion value that make StrictVersion happy.

Note that in both environment configure script find compiler tools
prefixed as example by "i586-pc-mingw32-".
My mingw is build for host "i386-mingw32msvc"(this isn't correct, but is
acceptable for host. For next version I plan to use for build the
correct one, i.e i386-pc-mingw32). So in the final Makefile I see:
CC= i386-mingw32msvc-gcc
AR= i386-mingw32msvc-ar
RANLIB= i386-mingw32msvc-ranlib

Also setup.py set compiler attribute linker_so - for details see
comments in the patch.

Another point is to link installed python in top-build directory so that
on posix system distutils read variables from our makefile instead from
installed in build system. In this case python_build (an internal to
distutils flag) is set.

A, but not common, build issue is that some python 2.4 versions will
search for pyconfig-32.h instead pyconfig.h.
Symptoms:
===

running build
running build_ext
error: ./pyconfig-32.h: No such file or directory

===
I see this on cent-os (5.0?), but I can't see on slackware 11.0.
This patch don't address this.
Just go in top-build directory and create a link, i.e. "ln -s
./pyconfig.h pyconfig-32.h".


If you system support emulation after build you may run python.
The build python search for modules. After patch modules are with suffix
same as for native build - .pyd. You may thin them to the top-build
directory or to follow binary distribution - create directory DLLs,
enter into it and link pyd-files:
$ for f in ../build/lib.*/*.pyd; do ln -sf $f; done


Differences between mingw build python and binary distribution(native
build):
Mingw build follow posix rules and will create more modules than native
build. In the native build they are part from main executable(buildin).
This is the list:
array, audioop, binascii, _bisect, _bytesio, cmath, _codecs_cn,
_codecs_hk, _codecs_iso2022, _codecs_jp, _codecs_kr, _codecs_tw,
_collections, cPickle, cStringIO, _csv, datetime, _fileio, _functools,
future_builtins, _heapq, _hotshot, imageop, itertools, _json, _locale,
_lsprof, math, mmap, msvcrt, _multibytecodec, operator, parser, _random,
strop, _struct, _subprocess, time, _weakref, _winreg, zlib.
I think that this inconsistency is problem of native build and for now I
don't address it.

Because in my environment I still don't have installed mingw port for
s

[issue3870] Parser/asdl_c.py requires python in order to build python

[Gregory P. Smith]

Changes by Gregory P. Smith <[EMAIL PROTECTED]>:


--
title: Parser/adsl_c.py requires python in order to build python -> 
Parser/asdl_c.py requires python in order to build python

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3870] Parser/adsl_c.py requires python in order to build python

[Gregory P. Smith]

New submission from Gregory P. Smith <[EMAIL PROTECTED]>:

Parser/asdl_c.py starts with  "#! /usr/bin/env python"  and is required
when building python.  The prevents python from being built on systems
without an existing python interpreter installed.  Which came first, the
python or the egg?

found when attempting to build python from subversion on FreeBSD 6.3.

This is what make trys to run that fails:

 ./Parser/asdl_c.py -h ./Include Parser/Python.asdl

--
components: Build
messages: 73238
nosy: gregory.p.smith
priority: normal
severity: normal
status: open
title: Parser/adsl_c.py requires python in order to build python
type: compile error
versions: Python 2.5, Python 2.6, Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

[Gregory P. Smith]

Changes by Gregory P. Smith <[EMAIL PROTECTED]>:


--
nosy: +gregory.p.smith

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3869] Arrow keys not working with Python 2.6rc1

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


--
resolution:  -> invalid
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3869] Arrow keys not working with Python 2.6rc1

[Daniel]

Daniel <[EMAIL PROTECTED]> added the comment:

That was it.

Needed to install libreadline5-dev.

Then the default settings for readline in Modules/setup needs
uncommented (line 165 in the current version) and it works.

Thank you kindly.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3617] Add MS EULA to the list of third-party licenses in the Windows installer

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

This is now fixed in r66460 and r66462; the text that gets included is
in Tools/msi/crtlicense.txt.

--
keywords:  -easy
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3869] Arrow keys not working with Python 2.6rc1

[Gregory P. Smith]

Gregory P. Smith <[EMAIL PROTECTED]> added the comment:

ubuntu?  make sure you have the libreadline5-dev package installed. 
then make distclean && ./configure && make

--
nosy: +gregory.p.smith
priority:  -> normal

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3869] Arrow keys not working with Python 2.6rc1

[Daniel]

Daniel <[EMAIL PROTECTED]> added the comment:

Yes I did the configure / compile myself.

After reading about readline in setup I am still unable to enable it but
I guess it is not a bug in Python but more a user problem.

I am quite puzzled as to why something like this would stop being
enabled by defualt tho, pretty sure I don't know anyone who doesn't use
input history.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1641] asyncore delayed calls feature

[Giampaolo Rodola']

Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>:


--
components: +Library (Lib) -Installation
versions: +Python 2.7, Python 3.1 -Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1641] asyncore delayed calls feature

[Giampaolo Rodola']

Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file8977/asyncore.py

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1641] asyncore delayed calls feature

[Giampaolo Rodola']

Giampaolo Rodola' <[EMAIL PROTECTED]> added the comment:

I try to revamp this issue by attaching a new patch which improves the
work I did against asyncore last time.
The approach proposed in this new patch is the same used in the upcoming
pyftpdlib 0.5.0 version which has been largely tested and benchmarked.
In my opinion, without the addition of an eventual paired heap module
into the stdlib there are no significant faster ways to do this than
using the common heapq module.
The patch in attachment includes:

- various changes which improve the speed execution when operating
against the heap.
- a larger test suite.
- documentation for the new class and its methods.

Josiah, do you have some time to review this?

--
components: +Installation -Library (Lib)
Added file: http://bugs.python.org/file11490/asyncore.patch

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3825] Major reworking of Python 2.5.2 re module

[Giampaolo Rodola']

Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>:


--
nosy: +giampaolo.rodola

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

[Guilherme Polo]

Guilherme Polo <[EMAIL PROTECTED]> added the comment:

Can you check if it is not the itimer tests that are causing that ? I'm
interested in gathering some more info about the problem and hopefully
fixing it now. Take a look into issue2240 and verify if it is related to
your problem, please.

--
nosy: +gpolo

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3869] Arrow keys not working with Python 2.6rc1

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

This probably has something to do with your readline build? Did you
compile Python yourself?

--
nosy: +benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3869] Arrow keys not working with Python 2.6rc1

[Daniel]

New submission from Daniel <[EMAIL PROTECTED]>:

On Xubuntu 8.04. In Python2.5 arrow keys allowed you to scroll through
previous lines typed but with 2.6rc1 this stopped working and it's now
just typing the ^[[A^[[B^[[D^[[C characters.

--
messages: 73229
nosy: Chewie
severity: normal
status: open
title: Arrow keys not working with Python 2.6rc1
type: behavior
versions: Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3690] sys.getsizeof wrong for Py3k bool objects

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

>> In any case, I also think this doesn't matter much either way. 
> Why do you think so?

What's the actual difference that this change makes? At most 8
bytes per object, right? And for two objects in total. So if somebody
would compute memory consumption, they might be off by not more
than 14 bytes, in total. Compared to all the other errors that memory
computation makes (e.g. malloc headers, rounding-up to multiples of
8 in obmalloc) which aren't accounted-for in sys.getsizeof, this
difference is negligible.

What's more, the small_ints aren't dynamically allocated, either,
but instead, each small_int takes a complete PyLongObject. If
that was also considered in long_sizeof, the computation would happen
to be completely correct for bool also.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3866] int() doesn't 'guess'

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Thanks for the suggestion! Fixed in r66459.

--
nosy: +benjamin.peterson
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3859] test_sys.Sizeof fails on win64

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Looks good to me.

--
keywords:  -needs review
nosy: +benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[Wurfpost] Invitation to indoor coed tournament 'Schreeuw van de Meeuw'

[Roelof Wentzel]

Ladies and gentlemen,

The indoor season starts again with an indoor coed tournament in Nijmegen. You 
can subscribe to this tournament by sending an e-mail to [EMAIL PROTECTED] 
Subscription to this tournament is open till 3th of October. 

Further information:
  a.. Date: 25th and 26th of October
  b.. Location: Nijmegen (Netherlands)
  c.. Food: dinner and breakfast
  d.. Party: two steps away from sportscentre with the band 'Million Dollars 
Babes' 
  e.. Costs: € 90 teamfee, €15 playersfee 
  f.. Number of players: at least 3 women and 3 man
More info will follow soon at www.ru.nl/bfrisbee2s/.

Regards,

Jaap, Nico & Roelof___
Wurfpost mailing list
Wurfpost@uni-koblenz.de
http://list.uni-koblenz.de/mailman/listinfo/wurfpost

[issue3862] test_array fails on FreeBSD7 amd64

[Reed O'Brien]

Reed O'Brien <[EMAIL PROTECTED]> added the comment:

2.6rc2 and Python-3.0b3 test_array detail
 
test_alloc_overflow (test.test_array.DoubleTest) ... Killed

Fills swap space and dumps core.


2.5.2 

test_list
test_addmul (test.test_list.ListTest) ... ok
test_append (test.test_list.ListTest) ... ok
Killed

The FreeBSD ports patches fix this in 2.5.2. Specifically patching
seq_tests.py to limit test_bigrepeat() to  if sys.maxint <= 2147483647.
no other tests fail; so I don't know immediately what else is patched.
Although there are about 25 patches for the 2.5 port.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3868] patch for review: OS/2 EMX port fixes for 2.6

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

The patches look good to me. 
I first thought that there could be a difference between PyOS_strnicmp 
and PyOS_mystrnicmp, but both Microsoft's strnicmp and python's PyOS_mystrnicmp 
are sensitive to the current locale.

Another unrelated issue is to protect all uses of Py_NAN: some builds 
may choose to #define Py_NO_NAN...

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3781] warnings.catch_warnings fails gracelessly when recording warnings but no warnings are emitted

[Nick Coghlan]

Changes by Nick Coghlan <[EMAIL PROTECTED]>:


--
keywords: +needs review

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3781] warnings.catch_warnings fails gracelessly when recording warnings but no warnings are emitted

[Nick Coghlan]

Nick Coghlan <[EMAIL PROTECTED]> added the comment:

3.0 version of the patch attached (it turned that it wasn't so much
test_support itself that caused the forward port problems, as the fact
that most of the tests that use this feature in 2.x are testing
specifically for Py3k warnings, or for other deprecated features that
aren't part of 3.0, so many of the changes either weren't needed, or
their contexts had changed completely).

Added file: 
http://bugs.python.org/file11489/issue3781_catch_warnings_cleanup_py3k.diff

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3680] Cycles with some iterator are leaking.

[Robert Schuppenies]

Robert Schuppenies <[EMAIL PROTECTED]> added the comment:

> I think it's ok, since the underlying containers will get cleared, thus
> breaking the cycle.

What about the dictiter object which references a tuple (di_result)?
Tuple does not implement tp_clear, but OTOH tuples are immutable and
di_result cannot be assigned.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Andrew I MacIntyre]

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment:

2.6rc1 shows the same failure traceback on FreeBSD 6.3, which is covered
by a section of setup.py the same as Damien added for OpenBSD.

--
nosy: +aimacintyre

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3861] distutils CCompiler._compile doesn't require lang keyword argument

[Mike Auty]

Mike Auty <[EMAIL PROTECTED]> added the comment:

You're absolutely right, it was a Gentoo patching issue.  Thanks very
much for the link to the bug, I would never have found it myself!  5:)

I'm off to go try and convince them it's a bad idea to patch interfaces...

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3861] distutils CCompiler._compile doesn't require lang keyword argument

[Amaury Forgeot d'Arc]

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>:


--
resolution:  -> invalid
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3861] distutils CCompiler._compile doesn't require lang keyword argument

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Your problem seems very similar to http://bugs.gentoo.org/219238
but it seems that the Gentoo installation uses a patched version of 
python. there is no "lang" parameter at all in the official version...

Do you use a patched version of python?

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3861] distutils CCompiler._compile doesn't require lang keyword argument

[Mike Auty]

Mike Auty <[EMAIL PROTECTED]> added the comment:

Sorry, scratch that, it turned out to be a patch added by a local
packager.  I don't seem to be able to close my own bug, but for anyone
who's triaging this, please mark this as CLOSED/INVALID or similar. 
Sorry for the inconvenience...

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3868] patch for review: OS/2 EMX port fixes for 2.6

[Andrew I MacIntyre]

New submission from Andrew I MacIntyre <[EMAIL PROTECTED]>:

The 2 attached patch files are patches required for the OS/2 EMX port to
build and function:
- build_os2emx.patch - updates to the Makefile and config files in
PC/os2emx;
- source_os2emx.patch - updates to various core/library/test files.
=> Include/pystrcmp.h (OS/2 is like Windows, with the same C lib routines)
=> Lib/test/test_io.py (OS/2 is like Windows again)
=> Objects/floatobject.c (should use macro'd symbols not direct)
=> Python/pymath.c (any platform without HAVE_LOG1P should have
DBL_EPSILON in )

For review so that the fixes can be rolled into 2.6 final.

Added file: http://bugs.python.org/file11488/source_os2emx.patch

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3865] explain that profilers should be used for profiling, not benchmarking

[Fredrik Lundh]

Fredrik Lundh <[EMAIL PROTECTED]> added the comment:

(the reason this is extra bad for C modules is that the profilers
introduce overhead for Python code, but not for C-level functions.  For
example, using the standard profiler to benchmark parser performance for
xml.etree.ElementTree vs. xml.etree.cElementTree will make ET appear to
be about 10 times slower than it actually is.)

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3868] patch for review: OS/2 EMX port fixes for 2.6

[Andrew I MacIntyre]

Changes by Andrew I MacIntyre <[EMAIL PROTECTED]>:


--
components: Build, Interpreter Core, Library (Lib), Tests
files: build_os2emx.patch
keywords: patch, patch
nosy: aimacintyre
severity: normal
status: open
title: patch for review: OS/2 EMX port fixes for 2.6
versions: Python 2.6
Added file: http://bugs.python.org/file11487/build_os2emx.patch

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3867] What's New in 2.6 doesn't mention stricter object.__init__

[Benjamin Peterson]

Changes by Benjamin Peterson <[EMAIL PROTECTED]>:


--
assignee: georg.brandl -> akuchling
nosy: +akuchling

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3867] What's New in 2.6 doesn't mention stricter object.__init__

[Andrew Bennetts]

New submission from Andrew Bennetts <[EMAIL PROTECTED]>:

http://bugs.python.org/issue1683368 changed object.__init__ so that
rejects args/kwargs.  This change should be mentioned in the "What's New
in Python 2.6" document, probably under the "Porting to Python 2.6" heading.

(I noticed this because the stricter object.__init__ has made Python
2.6rc1 (and probably earlier) incompatible with Bazaar, which in one or
two places happened to depend on the pre-2.6 behaviour.)

--
assignee: georg.brandl
components: Documentation
messages: 73215
nosy: georg.brandl, spiv
severity: normal
status: open
title: What's New in 2.6 doesn't mention stricter object.__init__
versions: Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3866] int() doesn't 'guess'

[Kent Johnson]

New submission from Kent Johnson <[EMAIL PROTECTED]>:

The library reference for int() says, "If radix is zero, the proper
radix is guessed based on the contents of string; the interpretation is
the same as for integer literals." The use of the word 'guess' implies
that there is some heuristic used here, that somehow the function will
look at an arbitrary number and figure out the correct radix. This can
confuse newbies:
http://mail.python.org/pipermail/tutor/2008-September/064268.html

'determined' might be a better word. For bonus points link to the
Language Reference page on integer literals:
http://docs.python.org/ref/integers.html

--
assignee: georg.brandl
components: Documentation
messages: 73214
nosy: georg.brandl, kjohnson
severity: normal
status: open
title: int() doesn't 'guess'
versions: Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3865] explain that profilers should be used for profiling, not benchmarking

[Fredrik Lundh]

New submission from Fredrik Lundh <[EMAIL PROTECTED]>:

You often see people using the profiler for benchmarking instead of
profiling.  I suggest adding a note that explains that the profiler
modules are designed to provide an execution profile for a given
program, not for benchmarking different libraries or, even worse,
benchmarking Python code against C libraries.  Point people to the
"timeit" module if they want resonably accurate results.

(and yes, it would be nice if the copyright text on the page

http://docs.python.org/dev/library/profile.html

was moved to the bottom of the page.  If necessary, add something like
"This description of the profile module is Copyright © 1994, by InfoSeek
Corporation, all rights reserved.  Full copyright message below" at the
top.)

--
assignee: georg.brandl
components: Documentation
messages: 73213
nosy: effbot, georg.brandl
severity: normal
status: open
title: explain that profilers should be used for profiling, not benchmarking
type: feature request
versions: Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

[Andrew I MacIntyre]

Changes by Andrew I MacIntyre <[EMAIL PROTECTED]>:


--
versions: +Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

[Andrew I MacIntyre]

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment:

I should add that this is a regression of the trunk, as I built and
tested the trunk from an SVN checkout (r63892) in early June and didn't
encounter this issue.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3862] test_array fails on FreeBSD7 amd64

[Andrew I MacIntyre]

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment:

2.6rc1 test_array passes on FreeBSD 6.3 i386.  I don't have a 7.0 box
(either i386 or amd64) accessible at the moment to cross check.

Can you run the test on its own in verbose mode to get a bit more of an
idea where its blowing up? - ie:

[EMAIL PROTECTED] ./python -E -tt Lib/test/regrtest.py -v test_array

from the build directory.

--
nosy: +aimacintyre

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3690] sys.getsizeof wrong for Py3k bool objects

[Robert Schuppenies]

Robert Schuppenies <[EMAIL PROTECTED]> added the comment:

As I understood the long object allocation it is implemented as
"PyObject_MALLOC(sizeof(PyVarObject) + size*sizeof(digit))" to avoid
this allocation of extra 2 bytes. So from my understanding, the number 0
allocates memory for the reference count, type, and ob_size, whereas any
other number allocates this plus additional memory required by the
number of digits.

Looking at bool objects in Py3k, arn't they fixed-sized memory-wise,
always allocating the the padded size of _longobject?

> In any case, I also think this doesn't matter much either way. 
Why do you think so?

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3111] multiprocessing ppc Debian/ ia64 Ubuntu compilation error

[Nick Coghlan]

Nick Coghlan <[EMAIL PROTECTED]> added the comment:

Scratch that - it's more likely to be Neal's setup which is at fault,
which I will be questioning on python-dev shortly (there are 3 other
tests which are failing/getting skipped in Neal's regression test suite)

--
priority: release blocker -> normal

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3111] multiprocessing ppc Debian/ ia64 Ubuntu compilation error

[Nick Coghlan]

Nick Coghlan <[EMAIL PROTECTED]> added the comment:

Setting this to a release blocker, because it is affecting Neal's
automated execution of the regression test suite with a debug build.

--
nosy: +ncoghlan
priority:  -> release blocker

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com