Difference between revisions of "Python3/SprintPycon2014"
(→What) |
|||
| Line 84: | Line 84: | ||
* [http://techs.enovance.com/6521/openstack_python3 Why should OpenStack move to Python 3 right now?] | * [http://techs.enovance.com/6521/openstack_python3 Why should OpenStack move to Python 3 right now?] | ||
| − | == | + | == Synchronizations == |
| − | Participants | + | === Participants === |
| − | * Victor Stinner | + | * Victor Stinner (organizer) |
* Chmouel Boudjnah | * Chmouel Boudjnah | ||
* Frederic Lepied | * Frederic Lepied | ||
| + | * Doug Hellman (will review patches remotely) | ||
| + | |||
| + | === Synchronize work on OpenStack components === | ||
Any change in OpenStack must be carefully reviewed. Don't expect to see your changes commited immediatly, you will probably have to discuss with the "core developers" of each project to enhance your patch, to make it fit the coding style of the project. | Any change in OpenStack must be carefully reviewed. Don't expect to see your changes commited immediatly, you will probably have to discuss with the "core developers" of each project to enhance your patch, to make it fit the coding style of the project. | ||
| Line 102: | Line 105: | ||
* <nowiki>https://review.openstack.org/#/...</nowiki> | * <nowiki>https://review.openstack.org/#/...</nowiki> | ||
| − | == Synchronize work on OpenStack dependencies == | + | === Synchronize work on OpenStack dependencies === |
If you want to work on an OpenStack dependency, please modify the list below: | If you want to work on an OpenStack dependency, please modify the list below: | ||
Revision as of 16:47, 1 April 2014
Victor Stinner organizes a sprint to Port OpenStack to Python 3 during 4 days at Montreal (Canada) during Pycon Montreal 2014: between April, 14 (Monday) and April, 17 (Thursday). See Pycon Montreal 2014 sprints.
Contents
What
The ultimate goal is to port the whole OpenStack project to Python 3. The goal of the sprint is to port OpenStack components and OpenStack dependencies to Python 3, send patches to port as much code as possible.
If you don't know OpenStack at all, please join us to port modules to Python 3: MySQL-python, boto (see boto3), etc.
Or come to help us replacing eventlet with Trollius!
Who
Anyone knowing Python and OpenStack can participate!
When
April, 14 (Monday) and April, 17 (Thursday).
The next major release of OpenStack is "Icehouse", scheduled for April, 17.
Where
Montreal, at Pycon Montreal 2014.
Requirements
- Good knownledge of Python
- Bring a laptop
- Create an account on Launchpad: Launchpad: new account -- Launchpad is used as OpenID provider, it is at least needed to edit this wiki page, used for the sprint
To contribute to OpenStack:
- Basic knownledge of OpenStack
- Install DevStack (small setup of OpenStack written to hack OpenStack)
- and OpenStack projects, sign the CLA (can be done during the sprint)
Port OpenStack components to Python 3
First, see Python3#OpenStack_clients for the latest status.
- oslo incubator
- oslo.messaging
- swiftclient is almost done
- glanceclient
- heatclient (work in progress)
- neutronclient
- savannaclient
Other tasks:
- Replace nose with testr
- Replace eventlet with trollius! (very complex right now)
Port OpenStack dependencies to Python 3
First, see Python3#Dependencies for the latest status.
- boto
- jsonrpclib
- mysql-python: 2 pending pull requests
- oslosphinx
- pycadf
- python-ldap
- qpid-python
- rtslib-fb
- sphinxcontrib-docbookrestapi
- sphinxcontrib-httpdomain
- sphinxcontrib-pecanwsme
- sqlalchemy-migrate (in progress)
- suds
- thrift
- websockify
Document
- Python 3 wiki page
- OpenStack Style Guidelines
- Documentation of the six module
- Port Python 2 code to Python 3
- Status of the OpenStack port to Python 3
- Use the new asyncio module and Trollius in OpenStack
- Why should OpenStack move to Python 3 right now?
Synchronizations
Participants
- Victor Stinner (organizer)
- Chmouel Boudjnah
- Frederic Lepied
- Doug Hellman (will review patches remotely)
Synchronize work on OpenStack components
Any change in OpenStack must be carefully reviewed. Don't expect to see your changes commited immediatly, you will probably have to discuss with the "core developers" of each project to enhance your patch, to make it fit the coding style of the project.
If you want to work on a component (ex: neutron, nova, etc.), please write the component name with your name below:
- <component>: <developer name>
If you send a patch, please add it to the list below:
- https://review.openstack.org/#/...
Synchronize work on OpenStack dependencies
If you want to work on an OpenStack dependency, please modify the list below:
- <python project>: <developer name>
If you send a patch, pull request, whatever, please add it to the list below:
- <project>: <url to patch>
