On Wed, Jun 24, 2015 at 9:48 PM, Stefan Behnel wrote:
>
>
> I'd wait with that a bit, though, until after Py3.5 is finally released
> and the actual needs for C code that want to use the new
> features become clearer.
>
I strongly disagree.
What we would end up with is 3rd party extension module
A type slot for tp_as_async has already been added (which is good!) but we
do not currently seem to have protocol functions for awaitable types.
I would expect to find an Awaitable Protocol listed under Abstract Objects
Layer, with functions like PyAwait_Check, PyAwaitIter_Check, and
PyAwaitIter_N
Hey Yeswanth
Students who get involved with the projects they plan to work with early
have a definite edge over students who don't, so certainly get involved
now. While I would highly encourage you to get involved with python-dev
(core projects are top in line), you may also want to consider 3rd
Personally, I'd like to celebrate the upcoming Python 3.2 release (which
will hopefully include 3to2) with moving all packages which do not have the
'Programming Language :: Python :: 3' classifier to a "Legacy" section of
PyPI and offer only Python 3 packages otherwise. Of course put a banner at
I would suggest that if packages that do not have Python 3 support yet are
listed, then their alternatives should also.
PyQt has had Py3 support for some time.
PostgreSQL and SQLite do (as does SQLAlchemy)
CherryPy has had Py3 support for the last release cycle
libxml2 does not, but lxml does.
Al
python-commandments.org is owned and hosted by the same person (Allen Short
aka dash aka washort) as pound-python.org which is the "official" website
for #Python and which links to it.
#Python is co-managed by Stephen Thorne (aka Jerub) and Allen Short (aka
dash aka washort). According to Freenod
Just because legacy Python needs to be kept around for a bit longer for a
few uses does not mean that "Python 3 is not ready yet". Any decent package
system can have two or more versions of Python installed at the same time.
It is not "critical self-evaluation" to repeat "Python 3 is not ready" a
You mean Twisted support, because library support is at the point where
there are fewer actively maintained packages not yet ported than those which
are. Of course if your Python experience is hyper-focused to one framework
that isn't ported yet, it will certainly seem like a lot, and you guys who
David and his Google Summer of Code student, Shashwat Anand.
You can read Shashwat's weekly progress updates at http://l0nwlf.in/ or
subscribe to http://twitter.com/l0nwlf for more micro updates.
We have more than 30 paid students working on Python 3 tasks this year, most
of them participating un
I'm sure we can find you a mentor.
On Wed, Mar 24, 2010 at 1:16 PM, Joe Amenta wrote:
> On Fri, Mar 19, 2010 at 2:45 AM, Terry Reedy wrote:
>
>> On 3/19/2010 2:23 AM, Laurent Gautier wrote:
>>
>>> On 3/19/10 3:36 AM, C. Titus Brown wrote:
>>>
Hi all,
once again, the PSF has been
Hi Laurent
If your community project would like help porting to Python 3, and you feel
this work is enough for a student to work full time for several weeks on,
then please do add it to the GSoC ideas page on the wiki.
There will be another program running for high school students which is more
s
after all these years, some people still run AmigaOS.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
> +1
>
> Having a "Repository-URL", "Repository-Browse-URL" and a
> "Bug-Tracker-URL" field in PyPI would be a lot more usefule then
> comments and ratings.
>
>
+1
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/p
Nobody is claiming right to censor what people say about their software.
This is the Internet. There are blogs. Google and other search engines
find blogs quickly, and people who agree with the viewpoints expressed link
to them thus making the blog postings more visible. There are countless
oth
That's not going to happen. Stop trolling the python-dev list.
On Wed, Nov 4, 2009 at 1:20 PM, sstein...@gmail.com wrote:
> Maybe the 3.x line should just be put out of our misery, merged back to
> 2.7, 2.8, 2.9, and proceed as Glyph suggested in passing with increasing
> levels of deprecation u
I'm not aware of any currently active project that isn't in the process of
adding Py3 support (or who has already done so). By "most maintainers" I'm
referring to the long tail; the hundreds of 3rd party modules used in niche
cases and can be easily replaced by those who need the functionality the
+1 on ending with 2.6.
I'm the maintainer of 3rd party Python 3-only packages and have ported a few
modules that we needed with some help from the 2to3 tool. It's really not a
big deal - and Py3 really is a massive improvement.
The main thing holding back the community are lazy and/or obstinate
I'll make the argument that feedback is useful, comments are much less so
and a lot more work.
It would be more useful to allow package users post feedback, visible only
to the package maintainer, and also add support for bugtracker links/etc.
Is the intention of Pypi really to turn it into a soc
How about moving it to a new repository on hg.python.org? Give it more of
an "official" feel without the burden of being in theb cpython tree?
On Thu, Aug 27, 2009 at 7:43 PM, "Martin v. Löwis" wrote:
>
> Ok, so then it should be easy to generate some real interest out of
> it, right? E.g. a som
On Sat, Jun 27, 2009 at 6:59 PM, Christian Heimes wrote:
>
> Gratulations! You did a fantastic job! :)
+1 !
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailm
Enough is enough guys. As entertaining as this thread has been, shouldn't
we be focused on the 3.1 release?
Don't feed the trolls. Ok so one wandered in, but nobody needed to respond
and it can only get worse from here.
Please just flag the offending address(es) for moderation and ask them
poli
> Oh, I heartily endorse his suggestions! I just want to make sure that we
> make maximum use of students (and their code doesn't get tossed at the
> end of the summer, which has serious morale consequences ;)
This is my concern as well.
One of my past students pitched a core project and ended u
ality will help ensure usable code. They could vary in reward
based on how difficult the problem is and perhaps have some Python swag as
runner-up prizes.
It'd also be a great way to promote Python 3.
On Thu, Mar 19, 2009 at 10:00 PM, Steve Holden wrote:
> Arc Riley wrote:
> >
> That makes it a much better candidate for GHOP that SoC, which requires
> projects with a little more meat on them.
Yes it does.
Though many organizations have taken to funding their own GHOPs. Perhaps
this year PSF can use the SoC funds ($500/student) to host a bounty-sprint
program much lik
ed.
The markup complexity makes it much easier for students to navigate while
including the info Google suggested. I'm hoping someone from the python web
team will add the CSS class we need to greatly simplify it.
On Wed, Mar 18, 2009 at 8:16 PM, Daniel (ajax) Diniz wrote:
> Arc Riley wrote
On Wed, Mar 18, 2009 at 7:53 PM, Terry Reedy wrote:
> IDLE needs lots of attention -- more than any one experienced person is
> likely to have
>
>
I've actually heard this from several people, IDLE on Py3 etc
Who would be a good person to mentor such a project?
__
On Wed, Mar 18, 2009 at 6:26 PM, Raymond Hettinger wrote:
> Without help, it is going to take a long time to get many packages
> converted to 3.x.
I don't disagree, I just don't want to volunteer projects for something they
don't want.
Unless I misunderstand the situation, PIL doesn't seem app
On Wed, Mar 18, 2009 at 6:13 PM, Brett Cannon wrote:
>
> I would double-check Benjamin can do this since I don't think he will be
> 18 by the time GSoC starts. The FAQ at
> http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#mentor_eligibilityseems
> to suggest it won't be an i
On Wed, Mar 18, 2009 at 5:59 PM, Maciej Fijalkowski wrote:
> I think we need to ask first guys who spend their live maintaining
> libraries instead of just proposing "let's make some poor student port
> it to py3k", but I might be just wrong, I don't know.
I agree. Part of Summer of Code is abo
>
> > Note the SoC timeline;
> >
> http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline
> >
> > So maybe it won't work for 3.1, but perhaps 3.1.1? 3.2?
>
> Well, there won't be any major changes in 3.1.1, but 3.2 is definitely
> open.
Cool, these are of course details you can
I've heard from four people that improving 2to3 would be a great project
(plus many more suggesting "port X to Python 3" as project ideas).
Note the SoC timeline;
http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline
So maybe it won't work for 3.1, but perhaps 3.1.1? 3.2?
We
Hey guys/gals
Summer of Code is ramping up. Every year the common complaint is that not
enough Python core projects get proposed by students, and of course a big
reason for that is often the only encouragement we offer prospective
students is a link to the PEP index.
So let's make this year diff
32 matches
Mail list logo
