From anand.rsystems at gmail.com Sat Mar 5 11:34:07 2011
From: anand.rsystems at gmail.com (Anand Sharma)
Date: Sat, 5 Mar 2011 16:04:07 +0530
Subject: [Python-porting] Urgent need for QA Automation Engineer with Python
Scripting exp. for 6 Months+ for Mountain View, CA Position
In-Reply-To: <AANLkTi=kBJYo67viboV+b2Q1W0+sXwFxc7h_qBLfFOtC@mail.gmail.com>
References: <AANLkTi=kBJYo67viboV+b2Q1W0+sXwFxc7h_qBLfFOtC@mail.gmail.com>
Message-ID: <AANLkTi=-U2+MW3MdFOMGPnh6y1=oaTYTt+w3NyUUaukk@mail.gmail.com>
Hi,
* *
Urgent need for *QA* *Automation Engineer** **with Python Scripting** **exp.
* for *6 Months+ **for* *Mountain View, CA** *Position. Please have a look
on it & Plz send across your Latest profile along with following details
asked given below-
*In your mail please mention :*
1) your total US experience/ Your skillset :
2) Your Current location:
3) Immigration status
4) In case of H1 B : Your H1 holder
5) Expected Salary/Rate:
6) Whether any relocation Issues:
7) All contact details :
If you have any friend who fits the profile please ask him or her to also
contact me or send his/her resume
*Required Skills ?*
*Position: **QA* *Automation Engineer with Python Scripting exp.*
*Duration: 6 Months+*
*Location: Mountain View, CA*
*
*
*Skills Required :*
*Python, Quality Assurance, Automation,UNIX Shell*
*Job Description: *
As QA Automation Engineer, you will be responsible for the automating test
suites for our remote access and sharing application. You will be designing
and developing automation test scripts using Python, Silk test and other
tools while working closely with QA team and development Engineers.
*Essential Functions:*
?Implement frameworks and collaborate with QA and developers in the
development of automated testing scripts
?Develop and maintain automation test scripts for client -server and web
based applications using Python, Silk and other automation tools
?Maintain, extend and enhance automation harnesses and testing
infrastructure
?Design and develop new scenario based stress, verification and application
simulation tests
?Develop innovative approaches to accommodate schedule and resource
constraints using automation techniques
?Execute automated test scripts and document test results
?Identify new open source tools for automation
?Mentor other team members in automation
?Write clear bug report and validate bug fixes
?Work collaboratively with diverse teams
*Job Requirements: *
?Degree in computer science or related field
?6+ years of software test automation experience including load, functional,
regression and performance testing
?2+ years of experience in automating Java based client server applications
using Python and Silk Test
?Expertise in automating tests for scalability, performance, reliability and
overall functionality of the product
?Excellent scripting skills using Python, 4 script language for Silk Test,
Perl and other scripting languages
?Strong working knowledge of Linux, Windows and Mac OS
?Strong working knowledge of network protocols
?Ability to troubleshoot complex software / hardware configuration problems
?Experience in participating in testing activities throughout the entire
SDLC
?Excellent verbal and written communication skills
--
*Anand Prakash*
Assistant Manager - Resourcing
R Systems Inc.
A SEI-CMMi, PCMM Level 5 & ISO 27001 Company
5000 WindPlay Drive, Suite 5
El Dorado Hills,CA 95762
(Direct) 916-830-8884 | (Fax) 916-939-6348
Email ID : anand.prakash at rsystems.com
www.rsystems.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20110305/d2bcd80c/attachment.html>
From orsenthil at gmail.com Sat Mar 5 12:41:23 2011
From: orsenthil at gmail.com (Senthil Kumaran)
Date: Sat, 5 Mar 2011 19:41:23 +0800
Subject: [Python-porting] [Marked-Spam] Urgent need for QA Automation
Engineer with
In-Reply-To: <AANLkTi=-U2+MW3MdFOMGPnh6y1=oaTYTt+w3NyUUaukk@mail.gmail.com>
References: <AANLkTi=kBJYo67viboV+b2Q1W0+sXwFxc7h_qBLfFOtC@mail.gmail.com>
<AANLkTi=-U2+MW3MdFOMGPnh6y1=oaTYTt+w3NyUUaukk@mail.gmail.com>
Message-ID: <20110305114123.GA7049@kevin>
Please post this to http://www.python.org/jobs
Please don't spam a technical discussion list.
Thanks,
Senthil
From i30817 at gmail.com Sat Mar 12 13:01:05 2011
From: i30817 at gmail.com (Paulo Levi)
Date: Sat, 12 Mar 2011 12:01:05 +0000
Subject: [Python-porting] Porting 2.1 to 2.7 without source
Message-ID: <AANLkTikaY4oL_Ouo7=mvF_fceV3hD944Ax4+fbArD3PO@mail.gmail.com>
There is a rather old game, "Vampire the Masquerade: Bloodlines" that used a
cut down python 2.1 for scripts. I am trying (and failing) to port it to a
more complete python version, and thought 2.7 would be a nice target being
the last same major version.
Well, anyway, i only need to add 3 missing functions (troika original),
expose "void _PyObject_Del(PyObject *op)" that appears to have been hidden
around 2.3, set a new home based on the dll path and the game starts up
(full of errors of course).
One error in special is bothering me, since it appears to be caused by
changes to the PyTypeObject struct. Whenever one of the "cvar" objects that
troika binded to the half life 2 engine gets to a certain level of the
scripting engine, a pagefault is almost inevitable. These happen in the
"PyType_Ready(PyTypeObject *type)" function for the base class (that
bizarrely appears neither to be PyBaseObject_Type or NULL, but 8), and when
adding methods to the dict, and i stopped trying to fix it there here.
Strangely tp_name is "cvar" as expected.
Is this a impossible dream?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20110312/dac7294c/attachment.html>
From regebro at gmail.com Sat Mar 12 19:46:30 2011
From: regebro at gmail.com (Lennart Regebro)
Date: Sat, 12 Mar 2011 13:46:30 -0500
Subject: [Python-porting] Porting 2.1 to 2.7 without source
In-Reply-To: <AANLkTikaY4oL_Ouo7=mvF_fceV3hD944Ax4+fbArD3PO@mail.gmail.com>
References: <AANLkTikaY4oL_Ouo7=mvF_fceV3hD944Ax4+fbArD3PO@mail.gmail.com>
Message-ID: <AANLkTinwvoQ4W+bLWk-+w7Hj+oQEi6vZ4aTFmGVpqT-s@mail.gmail.com>
On Sat, Mar 12, 2011 at 07:01, Paulo Levi <i30817 at gmail.com> wrote:
> One error in special is bothering me, since it appears to be caused by
> changes to the PyTypeObject struct. Whenever one of the "cvar" objects that
> troika binded to the half life 2 engine gets to a certain level of the
> scripting engine, a pagefault is almost inevitable.
Wild guess: Could this have something to do with the changes to
conform with aliasing rules?
http://www.python.org/dev/peps/pep-3123/
From i30817 at gmail.com Sat Mar 12 23:47:45 2011
From: i30817 at gmail.com (Paulo Levi)
Date: Sat, 12 Mar 2011 22:47:45 +0000
Subject: [Python-porting] Porting 2.1 to 2.7 without source
In-Reply-To: <AANLkTinwvoQ4W+bLWk-+w7Hj+oQEi6vZ4aTFmGVpqT-s@mail.gmail.com>
References: <AANLkTikaY4oL_Ouo7=mvF_fceV3hD944Ax4+fbArD3PO@mail.gmail.com>
<AANLkTinwvoQ4W+bLWk-+w7Hj+oQEi6vZ4aTFmGVpqT-s@mail.gmail.com>
Message-ID: <AANLkTikHJyO6m9eb6Ov=tE0acH8T2bjdsoEHeXVOixV=@mail.gmail.com>
Well, i just used python source 2.1.3 (supposedly one minor version above
what troika used, and the same problem occurs though probably not on the
same place (i haven't bothered to track it down here, since it doesn't occur
on typeobject.c anymore). Anyway to disable that optimization in visual
studio c++ 6.0 to be sure it's not that?
On Sat, Mar 12, 2011 at 6:46 PM, Lennart Regebro <regebro at gmail.com> wrote:
> On Sat, Mar 12, 2011 at 07:01, Paulo Levi <i30817 at gmail.com> wrote:
> > One error in special is bothering me, since it appears to be caused by
> > changes to the PyTypeObject struct. Whenever one of the "cvar" objects
> that
> > troika binded to the half life 2 engine gets to a certain level of the
> > scripting engine, a pagefault is almost inevitable.
>
> Wild guess: Could this have something to do with the changes to
> conform with aliasing rules?
>
> http://www.python.org/dev/peps/pep-3123/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20110312/c9da4fc3/attachment.html>
From i30817 at gmail.com Sun Mar 13 05:26:05 2011
From: i30817 at gmail.com (Paulo Levi)
Date: Sun, 13 Mar 2011 04:26:05 +0000
Subject: [Python-porting] Porting 2.1 to 2.7 without source
In-Reply-To: <AANLkTikHJyO6m9eb6Ov=tE0acH8T2bjdsoEHeXVOixV=@mail.gmail.com>
References: <AANLkTikaY4oL_Ouo7=mvF_fceV3hD944Ax4+fbArD3PO@mail.gmail.com>
<AANLkTinwvoQ4W+bLWk-+w7Hj+oQEi6vZ4aTFmGVpqT-s@mail.gmail.com>
<AANLkTikHJyO6m9eb6Ov=tE0acH8T2bjdsoEHeXVOixV=@mail.gmail.com>
Message-ID: <AANLkTimrfN=hvqDD5m5o5CWUxKiQD57buLiUDGNo8ouR@mail.gmail.com>
Also a interesting incompatibility occurred that i've just noticed. The game
didn't recognize the bool type as a int (as it expected the expression)
although bool is a subtype of int.
When i put this in PyRun_String that went away:
r = PyRun_StringFlags(str, s, g, l, NULL);
if(r != NULL && PyBool_Check(r)){
if(r == Py_True)
return PyInt_FromLong(1L);
else
return PyInt_FromLong(0L);
}
return r;
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20110313/4e1d16be/attachment.html>
From regebro at gmail.com Sun Mar 13 12:44:02 2011
From: regebro at gmail.com (Lennart Regebro)
Date: Sun, 13 Mar 2011 07:44:02 -0400
Subject: [Python-porting] Porting 2.1 to 2.7 without source
In-Reply-To: <AANLkTikHJyO6m9eb6Ov=tE0acH8T2bjdsoEHeXVOixV=@mail.gmail.com>
References: <AANLkTikaY4oL_Ouo7=mvF_fceV3hD944Ax4+fbArD3PO@mail.gmail.com>
<AANLkTinwvoQ4W+bLWk-+w7Hj+oQEi6vZ4aTFmGVpqT-s@mail.gmail.com>
<AANLkTikHJyO6m9eb6Ov=tE0acH8T2bjdsoEHeXVOixV=@mail.gmail.com>
Message-ID: <AANLkTim3VvZKCzTLX-X0M8orwqzUZTnWxKRq_kueZZtH@mail.gmail.com>
On Sat, Mar 12, 2011 at 17:47, Paulo Levi <i30817 at gmail.com> wrote:
> Well, i just used python source 2.1.3 (supposedly one minor version above
> what troika used, and the same problem occurs though probably not on the
> same place (i haven't bothered to track it down here, since it doesn't occur
> on typeobject.c anymore). Anyway to disable that optimization in visual
> studio c++ 6.0 to be sure it's not that?
I don't know, but you can change
PyObject_HEAD_INIT(NULL)
0, /* ob_size */
to
PyVarObject_HEAD_INIT(NULL, 0)
That won't work on Python 2.5 or earlier, but it should work under
Python 2.6 and 2.7. I don't have any real reason to believe this to be
the problem, but it could be worth a try.
From i30817 at gmail.com Mon Mar 14 06:46:16 2011
From: i30817 at gmail.com (Paulo Levi)
Date: Mon, 14 Mar 2011 05:46:16 +0000
Subject: [Python-porting] Porting 2.1 to 2.7 without source
In-Reply-To: <AANLkTim3VvZKCzTLX-X0M8orwqzUZTnWxKRq_kueZZtH@mail.gmail.com>
References: <AANLkTikaY4oL_Ouo7=mvF_fceV3hD944Ax4+fbArD3PO@mail.gmail.com>
<AANLkTinwvoQ4W+bLWk-+w7Hj+oQEi6vZ4aTFmGVpqT-s@mail.gmail.com>
<AANLkTikHJyO6m9eb6Ov=tE0acH8T2bjdsoEHeXVOixV=@mail.gmail.com>
<AANLkTim3VvZKCzTLX-X0M8orwqzUZTnWxKRq_kueZZtH@mail.gmail.com>
Message-ID: <AANLkTi=2JwKaFbBynmO=-2qy2oRtGvmsfBu-PHpW1ae2@mail.gmail.com>
I'm confused. Isn't that only possible if you can control the source (or
have enough debugging skill)? I don't actually have a compilable form of the
source for the c extension, and i only see those structs initializations on
them.
On Sun, Mar 13, 2011 at 11:44 AM, Lennart Regebro <regebro at gmail.com> wrote:
> On Sat, Mar 12, 2011 at 17:47, Paulo Levi <i30817 at gmail.com> wrote:
> > Well, i just used python source 2.1.3 (supposedly one minor version above
> > what troika used, and the same problem occurs though probably not on the
> > same place (i haven't bothered to track it down here, since it doesn't
> occur
> > on typeobject.c anymore). Anyway to disable that optimization in visual
> > studio c++ 6.0 to be sure it's not that?
>
> I don't know, but you can change
>
> PyObject_HEAD_INIT(NULL)
> 0, /* ob_size */
>
> to
>
> PyVarObject_HEAD_INIT(NULL, 0)
>
> That won't work on Python 2.5 or earlier, but it should work under
> Python 2.6 and 2.7. I don't have any real reason to believe this to be
> the problem, but it could be worth a try.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20110314/40644cdc/attachment.html>
From regebro at gmail.com Mon Mar 14 10:44:33 2011
From: regebro at gmail.com (Lennart Regebro)
Date: Mon, 14 Mar 2011 05:44:33 -0400
Subject: [Python-porting] Porting 2.1 to 2.7 without source
In-Reply-To: <AANLkTi=2JwKaFbBynmO=-2qy2oRtGvmsfBu-PHpW1ae2@mail.gmail.com>
References: <AANLkTikaY4oL_Ouo7=mvF_fceV3hD944Ax4+fbArD3PO@mail.gmail.com>
<AANLkTinwvoQ4W+bLWk-+w7Hj+oQEi6vZ4aTFmGVpqT-s@mail.gmail.com>
<AANLkTikHJyO6m9eb6Ov=tE0acH8T2bjdsoEHeXVOixV=@mail.gmail.com>
<AANLkTim3VvZKCzTLX-X0M8orwqzUZTnWxKRq_kueZZtH@mail.gmail.com>
<AANLkTi=2JwKaFbBynmO=-2qy2oRtGvmsfBu-PHpW1ae2@mail.gmail.com>
Message-ID: <AANLkTi=00tocbU64ygbXWmjfnjjtjUK4sMyLMJiTNTFw@mail.gmail.com>
On Mon, Mar 14, 2011 at 01:46, Paulo Levi <i30817 at gmail.com> wrote:
> I'm confused. Isn't that only possible if you can control the source (or
> have enough debugging skill)? I don't actually have a compilable form of the
> source for the c extension, and i only see those structs initializations on
> them.
I'm sorry, I didn't take the "without source" comment seriously in
your topic, because that is obviously impossible. I thought you meant
something else. You can not support any new Python version without the
C-extensions source. It needs to be recompiled.
--
Lennart Regebro: http://regebro.wordpress.com/
Python 3 Porting book: http://python3porting.com/
+33 661 58 14 64
From regebro at gmail.com Tue Mar 15 19:05:24 2011
From: regebro at gmail.com (Lennart Regebro)
Date: Tue, 15 Mar 2011 14:05:24 -0400
Subject: [Python-porting] PyCon Zope sprint Python 3 progress report /
roadmap.
Message-ID: <AANLkTin62Z-ytx-A19rxW410LA3HneQD=_57xYA-p2UQ@mail.gmail.com>
We are here in Atlanta porting Zope stuff, and I've updated the
roadmap, so I thought I'd post it on zope-dev and python-porting, so
people know things are happening, and that they should have been here,
because PyCon was awesome!
So yesterday we've finished the porting of some low-hanging fruits,
and they are now just hanging around waiting for releases. The
complete roadmap for zope.component porting is here:
Done and released:
==================
setuptools (ie distribute)
zope.interface
zope.event
zope.exceptions
zope.testrunner
Low hanging fruit:
==================
zope.i18nmessageid: Done - not released
setuptools - Done
TODO: Trunk supports Python 3, not yet released.
zope.hookable: Done - not released
setuptools - Done
zope.testing - [test] Done, not released
TODO: Trunk supports Python 3, not yet released.
zope.proxy: Done - not released
setuptools - Done
zope.interface - Done
TODO: Trunk supports Python 3, not yet released.
zope.testing: Done - not released
setuptools - Done
zope.interface - Done
zope.exceptions - Done
TODO: Trunk supports Python 3, not yet released.
zope.testrunnner: Done
setuptools - Done
zope.interface - Done
zope.exceptions - Done
zope.testing - [test] Done, not released
TODO: Some cleanup needed after releasing zope.testing for Python 3.
Mid hanging fruit:
==================
zope.configuration:
setuptools - Done
zope.interface - Done
zope.i18nmessageid - Done, not released
zope.schema
transaction:
zope.interface - Done
zc.lockfile:
setuptools - Done
ZConfig:
None
zdaemon:
None
manuel:
setuptools - Done
zope.testrunner - Done, waiting for zope.testing.
zope.testing - [test] Done, not released
High hanging fruit:
===================
zc.buildout: In Progress
setuptools - Done
zope.testing - [test] Done, not released
zope.component:
setuptools - Done
zope.interface - Done
zope.event - Done
zope.testing - [test] Done, not released
zope.testrunner - [test] Almost done, waiting for zope.testing.
zope.hookable - [hook] [test] Done, not released
zope.i18nmessageid - [zcml] Done, not released
zope.proxy - [security]
zope.location - [security] (Note semi-circular dependency)
zope.security - [security] (Note semi-circular dependency)
zope.configuration - [zcml]
ZODB3 - [persistentregistry] [test]
COMMENT: Loads of tests, mostly doctests means this is a pain to port. Also
there is loads of magic which also may be a pain to port. Lastly, to run all
the tests, we need a lot of extra modules, and some of those require
zope.component. So we need to run only some tests under Python 3, and add
tests once we port the other modules.
zope.component dependencies
===========================
Optional packages for zope.component. Should be ported directly after
zope.component. I don't know how difficult these are to port.
zope.schema:
setuptools - Done
zope.interface - Done
zope.event - Done
zope.testing - [test] Done, not released
z3c.recipe.sphinxdoc - [docs]
COMMENT: Sphinx isn't ported yet. That's only for docs though, so no biggie.
Possibly we'll have to avoid zc.buildout because of that.
zope.location:
setuptools - Done
zope.interface - Done
zope.proxy
zope.schema
zope.component - (Note semi-circular dependency)
zope.security: (Uses a c-module)
setuptools - Done
zope.interface - Done
zope.i18nmessageid - Done, not released
zope.proxy
zope.component - (Note semi-circular dependency)
zope.location
zope.schema
zope.testing - [test] Done, not released
ZODB3:
zope.event - Done
zope.interface - Done
transaction
zc.lockfile
ZConfig
zdaemon
zope.testing - [test] Done, not released
manuel - [test]
COMMENT: Once zope.testing and zc.buildout are done, merging Martins work
might not be too painful.
From barry at python.org Tue Mar 15 21:36:38 2011
From: barry at python.org (Barry Warsaw)
Date: Tue, 15 Mar 2011 16:36:38 -0400
Subject: [Python-porting] PyCon Zope sprint Python 3 progress report /
roadmap.
In-Reply-To: <AANLkTin62Z-ytx-A19rxW410LA3HneQD=_57xYA-p2UQ@mail.gmail.com>
References: <AANLkTin62Z-ytx-A19rxW410LA3HneQD=_57xYA-p2UQ@mail.gmail.com>
Message-ID: <20110315163638.4a1a5bdc@neurotica>
Lennart, great to see ztk packages getting ported to Python 3. I'm planning
on starting a serious Mailman 3 porting project once zope.component is
ported.
On Mar 15, 2011, at 02:05 PM, Lennart Regebro wrote:
>COMMENT: Loads of tests, mostly doctests means this is a pain to port.
I'm sure you know this, but doctests can be automatically converted via 2to3
by adding the following to your setup.py (assuming you use distribute):
setup(
...
# Auto-conversion to Python 3.
use_2to3=True,
convert_2to3_doctests=find_doctests(),
...
)
find_doctests() here being nothing specially, just an os.walk over your tree
to find the appropriate doctest files.
Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-porting/attachments/20110315/8e0605de/attachment.pgp>
From regebro at gmail.com Tue Mar 15 19:05:24 2011
From: regebro at gmail.com (Lennart Regebro)
Date: Tue, 15 Mar 2011 14:05:24 -0400
Subject: [Python-porting] [Zope-dev] PyCon Zope sprint Python 3 progress
report / roadmap.
Message-ID: <AANLkTin62Z-ytx-A19rxW410LA3HneQD=_57xYA-p2UQ@mail.gmail.com>
We are here in Atlanta porting Zope stuff, and I've updated the
roadmap, so I thought I'd post it on zope-dev and python-porting, so
people know things are happening, and that they should have been here,
because PyCon was awesome!
So yesterday we've finished the porting of some low-hanging fruits,
and they are now just hanging around waiting for releases. The
complete roadmap for zope.component porting is here:
Done and released:
==================
setuptools (ie distribute)
zope.interface
zope.event
zope.exceptions
zope.testrunner
Low hanging fruit:
==================
zope.i18nmessageid: Done - not released
setuptools - Done
TODO: Trunk supports Python 3, not yet released.
zope.hookable: Done - not released
setuptools - Done
zope.testing - [test] Done, not released
TODO: Trunk supports Python 3, not yet released.
zope.proxy: Done - not released
setuptools - Done
zope.interface - Done
TODO: Trunk supports Python 3, not yet released.
zope.testing: Done - not released
setuptools - Done
zope.interface - Done
zope.exceptions - Done
TODO: Trunk supports Python 3, not yet released.
zope.testrunnner: Done
setuptools - Done
zope.interface - Done
zope.exceptions - Done
zope.testing - [test] Done, not released
TODO: Some cleanup needed after releasing zope.testing for Python 3.
Mid hanging fruit:
==================
zope.configuration:
setuptools - Done
zope.interface - Done
zope.i18nmessageid - Done, not released
zope.schema
transaction:
zope.interface - Done
zc.lockfile:
setuptools - Done
ZConfig:
None
zdaemon:
None
manuel:
setuptools - Done
zope.testrunner - Done, waiting for zope.testing.
zope.testing - [test] Done, not released
High hanging fruit:
===================
zc.buildout: In Progress
setuptools - Done
zope.testing - [test] Done, not released
zope.component:
setuptools - Done
zope.interface - Done
zope.event - Done
zope.testing - [test] Done, not released
zope.testrunner - [test] Almost done, waiting for zope.testing.
zope.hookable - [hook] [test] Done, not released
zope.i18nmessageid - [zcml] Done, not released
zope.proxy - [security]
zope.location - [security] (Note semi-circular dependency)
zope.security - [security] (Note semi-circular dependency)
zope.configuration - [zcml]
ZODB3 - [persistentregistry] [test]
COMMENT: Loads of tests, mostly doctests means this is a pain to port. Also
there is loads of magic which also may be a pain to port. Lastly, to run all
the tests, we need a lot of extra modules, and some of those require
zope.component. So we need to run only some tests under Python 3, and add
tests once we port the other modules.
zope.component dependencies
===========================
Optional packages for zope.component. Should be ported directly after
zope.component. I don't know how difficult these are to port.
zope.schema:
setuptools - Done
zope.interface - Done
zope.event - Done
zope.testing - [test] Done, not released
z3c.recipe.sphinxdoc - [docs]
COMMENT: Sphinx isn't ported yet. That's only for docs though, so no biggie.
Possibly we'll have to avoid zc.buildout because of that.
zope.location:
setuptools - Done
zope.interface - Done
zope.proxy
zope.schema
zope.component - (Note semi-circular dependency)
zope.security: (Uses a c-module)
setuptools - Done
zope.interface - Done
zope.i18nmessageid - Done, not released
zope.proxy
zope.component - (Note semi-circular dependency)
zope.location
zope.schema
zope.testing - [test] Done, not released
ZODB3:
zope.event - Done
zope.interface - Done
transaction
zc.lockfile
ZConfig
zdaemon
zope.testing - [test] Done, not released
manuel - [test]
COMMENT: Once zope.testing and zc.buildout are done, merging Martins work
might not be too painful.
_______________________________________________
Zope-Dev maillist - Zope-Dev at zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
From palla74 at gmail.com Thu Mar 31 16:28:22 2011
From: palla74 at gmail.com (Palla)
Date: Thu, 31 Mar 2011 16:28:22 +0200
Subject: [Python-porting] EuroPython 2011: call for paper is ending - Please
spread the word!
Message-ID: <AANLkTimyzG8eswHPydj4KAQoe9L_zAPfqE9yNSEzzON5@mail.gmail.com>
Hi everyone,
I'm Francesco and I am writing on behalf of "Python Italia APS", a no-profit
association promoting EuroPython conference. (www.europython.eu)
Europython End of Call for Presentations is April 6th. I'd like to ask to
you to forward this mail to anyone that you feel may be interested.
We're looking for proposals on every aspects of Python: programming from
novice to advanced levels, applications and frameworks, or how you have been
involved in introducing Python into your organisation.
**First-time speakers are especially welcome**; EuroPython is a community
conference and we are eager to hear about your experience. If you have
friends or colleagues who have something valuable to contribute, twist their
arms to tell us about it!
Presenting at EuroPython
------------------------
We will accept a broad range of presentations, from reports on academic and
commercial projects to tutorials and case studies. As long as the
presentation is interesting and potentially useful to the Python community,
it will be considered for inclusion in the programme.
Can you show the conference-goers something new and useful? Can you show
attendees how to: use a module? Explore a Python language feature? Package
an application? If so, consider submitting a talk.
Talks and hands-on trainings
----------------------------
There are two different kind of presentations that you can give as a speaker
at EuroPython:
* **Regular talk**. These are standard "talk with slides", allocated in
slots of 45, 60 or 90 minutes, depending on your preference and scheduling
constraints. A Q&A session is held at the end of the talk.
* **Hands-on training**. These are advanced training sessions for a smaller
audience (10-20 people), to dive into the subject with all details. These
sessions are 4-hours long, and audience will be strongly encouraged to bring
a laptop to experiment. They should be prepared with less slides and more
source code. If possible, trainers will also give a short "teaser talk" of
30 minutes the day before the training, to tease delegates into attending
the training.
In the talk submission form, we assume that you intend to give a regular
talk on the subject, but you will be asked if you are available for also
doing a hands-on training on the very same subject.
Speakers that will give a hands-on training are rewarded with a **free
entrance** to EuroPython to compensate for the longer preparation required,
and might also be eligible for a speaking fee (which we cannot confirm at
the moment).
Topics and goals
----------------
Specific topics for EuroPython presentations include, but are not limited
to:
- Core Python
- Other implementations: Jython, IronPython, PyPy, and Stackless
- Python libraries and extensions
- Python 3.x migration
- Databases
- Documentation
- GUI Programming
- Game Programming
- Network Programming
- Open Source Python projects
- Packaging Issues
- Programming Tools
- Project Best Practices
- Embedding and Extending
- Science and Math
- Web-based Systems
Presentation goals usually are some of the following:
- Introduce audience to a new topic they are unaware of
- Introduce audience to new developments on a well-known topic
- Show audience real-world usage scenarios for a specific topic (case study)
- Dig into advanced and relatively-unknown details on a topic
- Compare different options in the market on a topic
Community-based talk voting
---------------------------
This year, for the first time in EuroPython history, the talk voting process
is fully public. Every partecipant gains the right to vote for talks
submitted during the Call For Papers, as soon as they commit to their
presence at the conference by buying a ticket. See all the details in the
talk voting[1] page.
Contacts
--------
For any further question, feel free to contact the organizers at
info at pycon.it. Thank you!
[1]: http://ep2011.europython.eu/talk-voting
--
->PALLA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20110331/29a9d2d8/attachment.html>