I use up-to-date Debian testing (wheezy), amd64 architecture. I compiled
and installed Python 3.3.0 alpha 3 using altinstall. Debian wheezy comes
with python3.2 (and 2.6 and 2.7). I installed the Debian package
python3-bs4 (BeautifulSoup). I also downloaded a clone developmental
copy of 3.3.
I use up-to-date Debian testing (wheezy), amd64 architecture. I compiled
and installed Python 3.3.0 alpha 3 using altinstall. Debian wheezy comes
with python3.2 (and 2.6 and 2.7). I installed the Debian package
python3-bs4 (BeautifulSoup4 for Python3). I also downloaded a clone
developmental
dpkg-architecture -qDEB_HOST_MULTIARCH
gives
x86_64-linux-gnu
Installing dpkg-dev fixed the problem. Now both 3.3a3 and a developmental
clone work.
There is already a Debian package for 3.3 alpha3.
See http://packages.debian.org/source/experimental/python3.3
A large diff for Debian Python is
I use up-to-date Debian testing (wheezy), amd64 architecture.
I have made a clone of the developmental version of Python 3.3.
make -s -j3 prints:
...
Python build finished, but the necessary bits to build these modules were
not found:
_bz2 _curses_curses_panel
_dbm
CPython 3.3.0a2 (default, Apr 24 2012, 10:47:03) [GCC 4.4.5]
Linux-2.6.32-5-amd64-x86_64-with-debian-6.0.4 little-endian
Ran make test. Hung during test_socket. Used CNTL-C to exit the test.
test_ssl failed. Ran ./python -m test -v test_ssl. Test ok. Ran
./python -m test -v test_socket which
Travis E. Oliphant wrote:
It also bothers me that so many ways to describe binary data are
being used out there. This is a problem that deserves being solved.
Is there a survey paper somewhere about binary formats? What formats are
used in particle physics, bio-informatics, astronomy, etc?
Python is a beautiful simple language with a rich standard library.
Python has done fine without a switch statement up to now. Guido left it
out of the original language for some reason (my guess is simplicity).
Why is it needed now? What would be added next: do while or goto? The
urge to add
Guido van Rossum wrote:
developers contributing code without wanting
to give up control are the problem.
That hits the nail on the head. If something is added to the standard
library, it becomes part of Python and must be controlled by whoever
controls Python. Otherwise there will be chaos.
Travis E. Oliphant [EMAIL PROTECTED] wrote:
It is very important for many people to get access to memory with some
description of how that memory should be interpreted as an array.
Several Python packages could benefit if Python had some notion of an
array interface that was at least
The contents page for the Python Library Reference
(http://docs.python.org/dev/lib/lib.html;) has become much too long. I
suggest that it should be designed like the top page for portal web
sites. For example see http://www.dmoz.org/;. I suggest that lib.html
be replaced by lib_index.html and
Guido van Rossen wrote:
I think the pattern hasn't been commonly known; people have been
struggling with setdefault() all these years.
I use setdefault _only_ to speed up the following code pattern:
if akey not in somedict:
somedict[akey] = list()
somedict[akey].append(avalue)
These
Guido van Rossum [EMAIL PROTECTED] wrote:
The discussion about PEP 343 reminds me of the following. Bram Cohen
pointed out in private email that, before PEP 342, there wasn't a big
need for a shortcut to pass control to a sub-generator because the
following for-loop works well enough:
def
Guido van Rossum wrote:
file = os.path.abspath(file) if file else '?'
...
These are all unreadable. In C a ? b : c is not used very often. A
quick check of the Python source found 476 occurences.
-1 to conditional expressions.
___
Python-Dev mailing
Here is an example from the Python Library Reference, Section 2.1
Built-in Functions:
class C(object):
def getx(self): return self.__x
def setx(self, value): self.__x = value
def delx(self): del self.__x
x = property(getx, setx, delx, I'm the 'x' property.)
It works. But if
According to the source code, PyTuple_Pack returns a new reference (it
calls PyTuple_New). It also Py_INCREF's all the objects in the new
tuple. Is this unusual behavior? None of these added references are
documented in the API Reference Manual.
___
Is there a C API for the built-in type set? if not, why not?
___
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/archive%40mail-archive.com
I had
PyArg_ParseTuple(args, s#s#i:compare, p1, bytes1, p2, bytes2)
in a program. There are not enough arguments to PyArg_ParseTuple. Does
PyArg_ParseTuple know how many arguments it is getting? If so, I suggest
that an exception should be raised here.
The relevant bug appears to be 1076467 at SourceForge.
___
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
18 matches
Mail list logo
