Re: Python talks at DebConf

2010-05-07 Thread anatoly techtonik 
On Tue, May 4, 2010 at 11:20 PM, Richard Darst  wrote:
>
> I was looking through the talks submitted to DebConf, and noticed
> there weren't very many Python related talks.  Given the amount there
> is to discuss related to Python in Debian, it would be great to see
> some more submissions.
>
> Perhaps the list can suggest some talks and we can nominate some
> people to lead them?  At least we should have a talk on Python
> packaging and one on packaging helpers.  Perhaps there could be talks
> on the DPMT or PAPT.  Any more ideas?

Only ideas.
"Using Python toolchain for Python modules/apps in Debian?"
Cover stdeb (anything else?), the reasons (if any) political and
technical, why it (or anything else) can not be used instead
unpythonic and unfamiliar make/debhelper stuff. It is not really
helper if no one understands how it works, and it is confusing for
non-C folks.

"Ubuntu, Debian and Python packaging."
Why the difference? The consequences.

"Python policy 2010."
Why not use virtualenv for Packaging applications?
Why stable Python packages should still be fetched from backports (Trac)?
How to use stable Python product compiled manually and still have an
automatic option for upgrade when official backport for the same
version is released?
How to customize/patch local installations of Python packages and sync
them with upstream? (MoinMoin patches, Trac Hacks, Roundup tweaks
etc).

"Python 3000"

Any speakers?
-- 
anatoly t.


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinmdz74hzzhyhl05ougyucx-r0poxsb8zoqr...@mail.gmail.com

Re: Python talks at DebConf

2010-05-07 Thread anatoly techtonik 
One more thing for "Python Policy 2010." Status quo with examples.

Trac comes with jQuery suitable for this version of application. But
Debian policy dictates to remove duplicated code, so jQuery is
replaced with some other version rather than required. This creates
problems with plugins and Debian email based tracker really suxx at
reporting problems with plugins from trac-hacks that were not ported
as packages (email based trackers suxx as a class). 80kb of duplicated
code (even 8Mb) doesn't worth wasted time for troubleshooting in 2010.
It may be a reason for security, but why not just let packages
register their used version in Debian registry and track it there?

BTW, on Windows I have tree 2.x Python versions installed and all
three are used even though only one is default. But there is no
Python2.6 even in backports on Lenny and I need it for python-expect,
to automate my stuff. This also requires explanation to refer people
when they ask.
-- 
anatoly t.


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktin3vt2vxilh0wvyxqnbd7dqelr1su94epmtm...@mail.gmail.com