On Fri, Apr 17, 2015 at 10:10 AM, Bryan Shook wrote:
> I saw Paul Tagliamonte's post to the debian-devel-announce list. I'd be
> interested in assisting with this project. I wrote some ctypes Python code
> that interacted with a Windows DLL. I ran into a lot of String encoding
> situations with
Hi,
Pygame supported python3 since before version 1.9.0 in 2009. All Pygame
code is written to work with either Python 2.x or 3.x. So building
Pygame for python3 is the same as for python2. Just use "python3
setup.py build" instead of "python setup.py build". Installation is also
the same. Fo
I saw Paul Tagliamonte's post to the debian-devel-announce list. I'd be
interested in assisting with this project. I wrote some ctypes Python code
that interacted with a Windows DLL. I ran into a lot of String encoding
situations with that. This would be my first time as a contributor to
Debian
One python package used heavilly in the raspberry pi community is
pygame. Unfortunately the package hasn't had an upstream stable release
since 2009 and the upstream stable release doesn't support python3.
Currently sid has the latest upstream stable release and no
python3-pygame package. Expe
On 16/04/15 14:50, Paul Tagliamonte wrote:
Aloha, Developers!
Many of our projects in Debian are written in Python -- yay, Python!
However, a large chunk are implemented in Python 2 -- Booo, Python 2!
Background
==
Python 2 is scheduled to be EOL'd upstream officially and for good i
On 04/16/2015 03:50 PM, Paul Tagliamonte wrote:
If you're interested in this effort, please email me. This is a really good new
contributor task, so if anyone's asked you how they could get involved with
Debian, you should send them to us!
/me raises hand
I'm interested! :)
Generally speaking
On Thursday, April 16, 2015 06:45:08 PM Stefano Rivera wrote:
> Hi Scott (2015.04.15_18:30:23_+0200)
>
> > If we are sharing dist-packages, then pypy can probably use the same
> > binary when the content would be the same. Only in cases where the
> > content is different would you duplicate a sepa
Hi Scott (2015.04.15_18:30:23_+0200)
> If we are sharing dist-packages, then pypy can probably use the same
> binary when the content would be the same. Only in cases where the
> content is different would you duplicate a separate pypy package.
That works, but only for leaf packages. Transitive de
On Thu, Apr 16, 2015 at 10:48 PM, Jan Dittberner wrote:
> Pyramid is a bit more lightweight
Flask might be another option for lightweight framework needs.
> Paul already suggested to merge debianmemberportfolio with db.debian.org but
> I did not have time to evaluate that option yet.
That is an
On Thu, Apr 16, 2015 at 02:30:16PM +0200, Nicolas Chauvat wrote:
> On Thu, Apr 16, 2015 at 02:58:53PM +0800, Paul Wise wrote:
> > Port services based on Pylons (deprecated) to something else like Django:
>
> Pylons is deprecated in favor of Pyramid. It could be that porting
> these services to Pyr
On Wednesday 15 April 2015 20:54:38 Barry Warsaw wrote:
> I'm up for helping too, of course.
Me too!
Kind regards,
--
Daniele Tricoli 'Eriol'
http://mornie.org
signature.asc
Description: This is a digitally signed message part.
On Apr 16, 2015, at 04:33 PM, Cyril Brulebois wrote:
>(Last time EOL approached, it was pushed back by 5 years, so…)
PEP 373 says that 2.7 will have bug fix releases until 2020. I suspect it
will continue to have security releases for some time after that, as long as
there's sufficient motivatio
Paul Tagliamonte (2015-04-16):
> Background
> ==
>
> Python 2 is scheduled to be EOL'd upstream officially and for good in 2020.
> We're in 2015 now (wow, that went quickly), and keeping our release cadence up
> (3 years a pop) puts Stretch up in 2018, and Buster in 2021.
Wheezy was firs
On Thu, Apr 16, 2015 at 02:58:53PM +0800, Paul Wise wrote:
> Port services based on Pylons (deprecated) to something else like Django:
Pylons is deprecated in favor of Pyramid. It could be that porting
these services to Pyramid will be easier than rewriting on top of Django.
--
Nicolas Chauvat
On Apr 16, 2015, at 10:07 AM, Karsten Hilbert wrote:
>Maybe /usr/bin/python can become a wrapper executing Python 2
>(like now) but also showing
>
> Python 2 will be deprecated in 2020 the latest.
> Do not use it to write new code.
> Consider helping in porting existing code.
>
On Apr 16, 2015, at 10:10 AM, Karsten Hilbert wrote:
>With all this desire to drop Python 2 eventually -- there are
>packages, say gnumed-client, which simply cannot be ported to
>Python 3 ATM because important dependencies don't exist for
>Py 3, say pythonX-wxgtk.
Right. The best approach is to
On Apr 16, 2015, at 02:58 PM, Paul Wise wrote:
>Does anyone know of any other deprecated Python stuff that we should
>move away from?
One of the things I'd like to see happen, probably from the PyPA (Python
Packaging Authority), is some help for determining this via PyPI. For
example, if you sea
With all this desire to drop Python 2 eventually -- there are
packages, say gnumed-client, which simply cannot be ported to
Python 3 ATM because important dependencies don't exist for
Py 3, say pythonX-wxgtk.
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 45
On Wed, Apr 15, 2015 at 04:27:51PM -0400, Paul Tagliamonte wrote:
> I'd like this to have the endorsement of the team, so, does anyone object to
> me asking people to not write new tools in Python 2 only (prefer alternative
> deps or porting), and only use Python 2 in very special curcumstances or
19 matches
Mail list logo
