PyAppsPkgs

Differences between revisions 2 and 3
Revision 2 as of 2010-01-26 20:17:44
Size: 165
Editor: pool-71-123-25-78
Comment: page was renamed from MeetingLogs/devweek1001/devweek1001/PyAppsPkgs
Revision 3 as of 2010-01-27 20:15:48
Size: 2753
Editor: pool-71-123-25-78
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
(03:05:34 PM) DktrKranz: Hello everybody, and thank you to be here at Python Application packaging hosted at Ubuntu Developer Week!
(03:05:52 PM) DktrKranz: My name is Luca Falavigna, I'm a MOTU and Debian Developer, and I'll be your SABPDFT (Self-Appointed Benevolent Python Dictator For Today) for the next minutes :)
(03:06:27 PM) DktrKranz: For those who weren't here last week, I already had a session about basic Python application packaging. You can find logs here: http://irclogs.ubuntu.com/2010/01/21/%23ubuntu-classroom.html
(03:06:59 PM) DktrKranz: It basically covered how to handle control files in debian/, and how to easily find dependencies for your Python applications. Even if you are good in Python packaging, there could be some interesting tips to improve your kung-fu :)
(03:07:21 PM) DktrKranz: Today we will look at some advanced tricks to improve overall Python packages quality and stability.
(03:07:43 PM) DktrKranz: But let's start with a really short introduction.
(03:08:14 PM) DktrKranz: I refer to a "Python application" as a piece of software composed by one or more Python scripts and eventually one of more modules (or "packages", distutils calls them that way).
(03:08:55 PM) DktrKranz: Other kinds of software are "Python modules", which contain modules potentially useful for other programs installed in the global namespace, and "Python extensions", which usually are C source files, compiled and liked for a given Python interpreter to extend its features.
(03:09:18 PM) DktrKranz: But how does a Python application look like?
(03:09:42 PM) DktrKranz: I've created a really dumb one for the occasion. Open your favourite terminal and launch dget -u http://people.debian.org/~dktrkranz/pythontest/pythontest_0.1-1/pythontest_0.1-1.dsc
(03:10:18 PM) DktrKranz: Once you've downloaded it, look at pythontest-0.1 directory, you will find pythontest script, PythonTest module (or "package") and setup.py, which is Python distutils' "makefile".
(03:11:03 PM) DktrKranz: It's probably the smallest Python application you'll ever seen, it just prints a message, and then exits :)
(03:11:19 PM) DktrKranz: Invest a couple of minutes to examine the few files available, then we will move to packaging.
(03:12:08 PM) DktrKranz: < Omar871> QUESTION: Will "setup.py install" work?
(03:12:31 PM) DktrKranz: Omar871: it should by launching "python setup.py install"
(03:13:21 PM) DktrKranz: I didn't test that way, but it should work as expected ;)
(03:15:24 PM) DktrKranz: < Omar871> QUESTION: How do I use the package after installing it?
...

Dev Week -- Python Applications Packaging -- DktrKranz -- Wed, Jan 27

UTC

(03:05:34 PM) DktrKranz: Hello everybody, and thank you to be here at Python Application packaging hosted at Ubuntu Developer Week!
(03:05:52 PM) DktrKranz: My name is Luca Falavigna, I'm a MOTU and Debian Developer, and I'll be your SABPDFT (Self-Appointed Benevolent Python Dictator For Today) for the next minutes :)
(03:06:27 PM) DktrKranz: For those who weren't here last week, I already had a session about basic Python application packaging. You can find logs here: http://irclogs.ubuntu.com/2010/01/21/%23ubuntu-classroom.html
(03:06:59 PM) DktrKranz: It basically covered how to handle control files in debian/, and how to easily find dependencies for your Python applications. Even if you are good in Python packaging, there could be some interesting tips to improve your kung-fu :)
(03:07:21 PM) DktrKranz: Today we will look at some advanced tricks to improve overall Python packages quality and stability.
(03:07:43 PM) DktrKranz: But let's start with a really short introduction.
(03:08:14 PM) DktrKranz: I refer to a "Python application" as a piece of software composed by one or more Python scripts and eventually one of more modules (or "packages", distutils calls them that way).
(03:08:55 PM) DktrKranz: Other kinds of software are "Python modules", which contain modules potentially useful for other programs installed in the global namespace, and "Python extensions", which usually are C source files, compiled and liked for a given Python interpreter to extend its features.
(03:09:18 PM) DktrKranz: But how does a Python application look like?
(03:09:42 PM) DktrKranz: I've created a really dumb one for the occasion. Open your favourite terminal and launch dget -u http://people.debian.org/~dktrkranz/pythontest/pythontest_0.1-1/pythontest_0.1-1.dsc
(03:10:18 PM) DktrKranz: Once you've downloaded it, look at pythontest-0.1 directory, you will find pythontest script, PythonTest module (or "package") and setup.py, which is Python distutils' "makefile".
(03:11:03 PM) DktrKranz: It's probably the smallest Python application you'll ever seen, it just prints a message, and then exits :)
(03:11:19 PM) DktrKranz: Invest a couple of minutes to examine the few files available, then we will move to packaging.
(03:12:08 PM) DktrKranz: < Omar871> QUESTION: Will "setup.py install" work?
(03:12:31 PM) DktrKranz: Omar871: it should by launching "python setup.py install"
(03:13:21 PM) DktrKranz: I didn't test that way, but it should work as expected ;)
(03:15:24 PM) DktrKranz: < Omar871> QUESTION: How do I use the package after installing it?
...

MeetingLogs/devweek1001/PyAppsPkgs (last edited 2010-01-29 10:07:29 by i59F765F3)