Zitat von "Juancarlo Añez (Apalala)" :
It seems that Jython is under the Python Foundation, but I can't
find a roadmap, a plan, or instructions about how to contribute to
it reaching 2.7 and 3.3.
Are there any pages that describe the process?
Hi Juanca,
These questions are best asked on
It seems that Jython is under the Python Foundation, but I can't find a
roadmap, a plan, or instructions about how to contribute to it reaching
2.7 and 3.3.
Are there any pages that describe the process?
Thanks in advance,
-- Juanca
___
Python-Dev
On Tue, Aug 21, 2012 at 3:08 AM, Brett Cannon wrote:
> Should that be "path-based"?
I don't mind either way. I ain't trawling through to change it
everywhere though - I've already done that once this week :)
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
_
On Tue, Aug 21, 2012 at 3:01 AM, Terry Reedy wrote:
>
>
> On 8/20/2012 3:14 AM, nick.coghlan wrote:
>>
>> +(5)
>> + :meth:`clear` and :meth:`!copy` are included for consistency with the
>> + interfaces of mutable containers that don't support slicing operations
>> + (such as :class:`dict` an
On 21Aug2012 02:39, Andrea Griffini wrote:
| On Mon, Aug 20, 2012 at 11:42 PM, Antoine Pitrou wrote:
| >> In the spirit of RawIO.write(), I think RawIO.writelines() could return
| >> the number of bytes written (allowing for partial writes).
|
| When dealing with a non-blocking IO what you norma
On Mon, Aug 20, 2012 at 11:42 PM, Antoine Pitrou wrote:
>> In the spirit of RawIO.write(), I think RawIO.writelines() could return
>> the number of bytes written (allowing for partial writes).
When dealing with a non-blocking IO what you normally do is use number
returned from the write call to m
On Mon, 20 Aug 2012 23:42:56 +0200, Antoine Pitrou wrote:
> On Mon, 20 Aug 2012 23:17:10 +0200
> Antoine Pitrou wrote:
> >
> > Hello,
> >
> > I was considering a FileIO.writelines() implementation based on
> > writev() and I noticed that the current RawIO.writelines()
> > implementation is brok
On Mon, 20 Aug 2012 23:17:10 +0200
Antoine Pitrou wrote:
>
> Hello,
>
> I was considering a FileIO.writelines() implementation based on
> writev() and I noticed that the current RawIO.writelines()
> implementation is broken: RawIO.write() can return a partial write but
> writelines() ignores the
Hello,
I was considering a FileIO.writelines() implementation based on
writev() and I noticed that the current RawIO.writelines()
implementation is broken: RawIO.write() can return a partial write but
writelines() ignores the result and happily proceeds to the next
iterator item (and None is retu
Should that be "path-based"?
On Sun, Aug 19, 2012 at 11:49 PM, nick.coghlan
wrote:
> http://hg.python.org/cpython/rev/2f9f5ab3d754
> changeset: 78664:2f9f5ab3d754
> user:Nick Coghlan
> date:Mon Aug 20 13:49:08 2012 +1000
> summary:
> s/path importer/path based finder/ (becaus
moro
___
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
On Aug 20, 2012, at 05:49 AM, nick.coghlan wrote:
> s/path importer/path based finder/ (because the path based finder is not an
> importer and the simpler 'path finder' is too ambiguous)
+1!
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
ht
12 matches
Mail list logo