Mailman 3 December 2008 - Python-Dev

Re: [Python-Dev] Should there be a way or API for retrieving from a code object a loader method and package file where the code comes from?
by Phillip J. Eby Dec. 23, 2008

Dec. 23, 2008

At 06:55 AM 12/23/2008 -0500, Rocky Bernstein wrote: >Now that there is a package mechanism (are package mechanisms?) like >zipimporter that bundle source code into a single file, should the >notion of a "file" location should be adjusted to include the package >and/or importer? > >Is there a standard API or routine which can extract this information >given a code object? The inspect module (in 2.5 and up) supports retrieving the source lines for any object that has module globals. So you could do it for a class, a function, a method, module-level code, or even a frame, but not for a standalone code object. I believe there are also certain inspect module APIs that will return a pseudo-filename, i.e. the zipfile name followed by the path within the zipfile. >Also I'm not sure there *is* a standard print string way to show >member inside a package. zipimporter may insert co_filename strings >like: > > /usr/lib/python2.5/site-packages/tracer-0.1.0-py2.5.egg/tracer.py AFAIK, it'll only do this if the zipfile doesn't contain a usable .pyc or .pyo. Ordinarily, co_filename will be the name of the original source file before the zipfile was created.

1 0

Releasing 2.5.4
by "Martin v. Löwis" Dec. 23, 2008

Dec. 23, 2008

It seems r67740 shouldn't have been committed. Since this is a severe regression, I think I'll have to revert it, and release 2.5.4 with just that change. Unless I hear otherwise, I would release Python 2.5.4 (without a release candidate) tomorrow. Regards, Martin

4 6

If I check something in ...
by skip＠pobox.com Dec. 23, 2008

Dec. 23, 2008

I have this trivial little test case for test_file.py: + def testReadWhenWriting(self): + self.assertRaises(IOError, self.f.read) I would like to add it to the 2.6 and 3.0 maintenance branch and the 2.x trunk and the py3k branch. What is the preferred way to do that? Do I really have to do the same task four times or can I check it in once (or twice) secure in the belief that someone will come along and do a monster merge? Thx, Skip

3 5

Re: [Python-Dev] [capi-sig] Exceptions with additional instance variables
by Guilherme Polo Dec. 22, 2008

Dec. 22, 2008

On Mon, Dec 22, 2008 at 10:06 AM, <chojrak11(a)gmail.com> wrote: > On Mon, Dec 22, 2008 at 03:29, Guilherme Polo <ggpolo(a)gmail.com> wrote: >> On Sun, Dec 21, 2008 at 11:02 PM, <chojrak11(a)gmail.com> wrote: >>> Hello, >>> >>> I'm trying to implement custom exception that have to carry some >>> useful info by means of instance members, to be used like: >>> >>> try: >>> // some code >>> except MyException, data: >>> // use data.errorcode, data.errorcategory, data.errorlevel, >>> data.errormessage and some others >>> >>> The question is - how to implement the instance variables with >>> PyErr_NewException? >> >> Using PyErr_NewException is fine. You must understand that an >> exception is a class, and thus PyErr_NewException creates one for you >> and returns it. >> Just like you would do with a class that has __dict__, set some >> attributes to what you want. That is, use PyObject_SetAttrString or >> something more appropriated for you. > > Ok so I did the following. In init function (forget refcounting and > error checking for a moment ;-) > > PyObject *dict = PyDict_New(); > PyDict_SetItemString(dict, "errorcode", PyInt_FromLong(0)); > static PyObject *myexception = > PyErr_NewException("module.MyException", NULL, dict); You do not really have to create a dict here, one will be created for you if you pass a NULL there. > PyModule_AddObject(module, "MyException", myexception); > > It worked more or less as expected, the help shown: > > | ---------------------------------------------------------------------- > | Data and other attributes defined here: > | > | errorcode = 0 > | > | ---------------------------------------------------------------------- > > Then I did the following when raising the exception: > > PyObject_SetAttrString(myexception, "errorcode", PyInt_FromLong(111)); > PyErr_SetString(myexception, "Bad thing happened"); > return NULL; > > and the test code was: > try: > do_bad_thing(); > except MyException, data: > > and you surely already guessed it -- data.errorcode was 0.... Not only > that, module.MyException.errorcode was also 0... > > What I'm doing wrong? I certainly don't get the idea of exceptions in > Python, especially what is being raised - a class or an instance? There are two forms raise can take, both will end up involving a class and a intsance. > If > the latter - how's the class instantiated? You can call a class to instantiate it. > If not - what about values > in different threads? The docs are so vague about that... > > > Thanks again in advance, > Chojrak > Again, an exception is a class, so you could create a new type in C, and do anything you wanted. But you probably don't want to create a new type to achieve this, so there are two simple ways I'm going to paste below: #include "Python.h" static PyObject *MyErr; static PyMethodDef module_methods[] = { {"raise_test", (PyCFunction)raise_test, METH_NOARGS, NULL}, {NULL}, }; PyMODINIT_FUNC initfancy_exc(void) { PyObject *m; m = Py_InitModule("fancy_exc", module_methods); if (m == NULL) return; MyErr = PyErr_NewException("fancy_exc.err", NULL, NULL); Py_INCREF(MyErr); if (PyModule_AddObject(m, "err", MyErr) < 0) return; } the raise_test function is missing, pick one of these: static PyObject * raise_test(PyObject *self) { PyObject_SetAttrString(MyErr, "code", PyInt_FromLong(42)); PyObject_SetAttrString(MyErr, "category", PyString_FromString("nice one")); PyErr_SetString(MyErr, "All is good, I hope"); return NULL; } or static PyObject * raise_test(PyObject *self) { PyObject *t = PyTuple_New(3); PyTuple_SetItem(t, 0, PyString_FromString("error message")); PyTuple_SetItem(t, 1, PyInt_FromLong(10)); PyTuple_SetItem(t, 2, PyString_FromString("category name here")); PyErr_SetObject(MyErr, t); Py_DECREF(t); return NULL; } In this second form you check for the args attribute of the exception. -- -- Guilherme H. Polo Goncalves

2 3

Python 3.0.1
by Barry Warsaw Dec. 22, 2008

Dec. 22, 2008

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to get Python 3.0.1 out before the end of the year. There are no showstoppers, but I haven't yet looked at the deferred blockers or the buildbots. Do you think we can get 3.0.1 out on December 24th? Or should we wait until after Christmas and get it out, say on the 29th? Do we need an rc? This question goes mostly to Martin and Georg. What would work for you guys? - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSUwgEXEjvBPtnXfVAQIthgP7BDS6xfBHhADKc50ANvZ5aAfWhGSU9GH/ DR+IRduVmvosu9gm92hupCOaLCN4IbtyFx27A8LQuPNVc4BVrhWfDKDSzpxO2MJu xLJntkF2BRWODSbdrLGdZ6H6WDT0ZAhn6ZjlWXwxhGxQ5FwEJb7moMuY7jAIEeor 5n6Ag5zT+e8= =oU/g -----END PGP SIGNATURE-----

7 11

python 2.5.3 segmentation fault with gcc 4.1.2
by Stijn De Weirdt Dec. 21, 2008

Dec. 21, 2008

hi all, i'm trying to build python 2.5.3 on centos5.2 x86_64 (base gcc is 4.1.2) output of env, configure, make -j and make test at http://users.ugent.be/~stdweird/python-gcc-seg.tar.gz this all seems ok (at least to me ;) but the following code gives a segfault instead of an IOerror fname='test123' f=open(fname,'w') f.read() (test123 doesn't exists. it is a reduced problem from a scipy unittest). with system python (2.4.3) i get: IOError: [Errno 9] Bad file descriptor any hints what might cause this (or how i can figure it out). i have a coredump, but have no clue what to look for. many thanks, stijn -- The system will shutdown in 5 minutes.

4 4

2.6.1 documentation not available for download
by Arfrever Frehtes Taifersar Arahesis Dec. 21, 2008

Dec. 21, 2008

Python 2.6.1 documentation currently isn't available for download at: http://docs.python.org/ftp/python/doc/ Additionally please include version numbers in documentation archives (e.g. python-docs-html-2.6.1.tar.bz2). -- Arfrever Frehtes Taifersar Arahesis

3 7

Re: [Python-Dev] Can't have unbuffered text I/O in Python 3.0?
by bcannon＠gmail.com Dec. 21, 2008

Dec. 21, 2008

On Dec 19, 2008 2:20pm, Fabio Zadrozny <fabiofz(a)gmail.com> wrote: > You're right, thanks (guess I'll use that option then). > > > > Now, is it a bug that Python 3.0 doesn't run unbuffered when > > specifying -u or PYTHONUNBUFFERED, or was this support dropped? > > Well, ``python -h`` still lists it. That means either the output for -h needs to be fixed or the feature needs to be supported. -Brett

5 6

2.6.1 license
by Steve Holden Dec. 20, 2008

Dec. 20, 2008

It might be helpful if http://www.python.org/download/releases/2.6.1/license/ said it was also the official license for the 2.6.1 release (though I don't suppose it matters that it's still called the 2.5 license, since that's its origin). Another detail to go into the release manage PEP? regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/

2 1

Distutils maintenance
by Tarek Ziadé Dec. 20, 2008

Dec. 20, 2008

Hello I would like to request a commit access to work specifically on distutils maintenance. Regards Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/

4 3