Re: [Python-Dev] Has python-dev collapsed?

2008-10-29 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Oct 28, 2008, at 04:17 PM, Guido van Rossum wrote:

>Yes, that's what it feels like. I hope the pace picks up again and we
>can release 3.0 final in early December still. I really don't want to
>carry it over to 2009.

Don't worry, it won't.  As I mentioned before, I've basically been unable to
work on any Python stuff these last two weeks.  I'll be back home on Saturday
so I can start looking at the 3.0 release blockers when I get back.  The
schedule still has us releasing Python 3.0 final on 3-Dec, and I'm hopeful we
can still meet that date.

- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkkIL0wACgkQ2YZpQepbvXHxOQCdFUA4Q3frOjG2GX1ME0hc6uoZ
niwAn3deTj4E9KO+K4dMHWlKhKbjbaga
=0Py5
-END PGP SIGNATURE-
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Has python-dev collapsed?

2008-10-29 Thread A.M. Kuchling
On Wed, Oct 29, 2008 at 12:26:48AM +0100, Christian Heimes wrote:
> Maybe we should select an assistant release manager for the next  
> releases. It's lots of work to handle two releases at the same time. A  

Will 3.1 and 2.7 also be parallel releases?  (I ask, not having read
the 3xxx PEPS at all.)  

If yes, why?  While I can see a case for 2.6/3.0 being in sync -- new
features in 2.6 ease the transition to 3.0 -- I'd imagine that 3.1
would be better with a shorter cycle (6-9 months) because there are
more possible rough edges to clean up.  3.1 would likely include
bugfixes from the eventual 2.7, so 3.1 might also trigger 2.6.1, but I
don't think there's any harm if 3.1 contains features or incompatible
fixes that are unavailable to 2.x users.

--amk
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Has python-dev collapsed?

2008-10-29 Thread glyph


On 29 Oct, 09:14 pm, [EMAIL PROTECTED] wrote:

Will 3.1 and 2.7 also be parallel releases?  (I ask, not having read
the 3xxx PEPS at all.)

If yes, why?  While I can see a case for 2.6/3.0 being in sync -- new
features in 2.6 ease the transition to 3.0 -- I'd imagine that 3.1
would be better with a shorter cycle (6-9 months) because there are
more possible rough edges to clean up.  3.1 would likely include
bugfixes from the eventual 2.7, so 3.1 might also trigger 2.6.1, but I
don't think there's any harm if 3.1 contains features or incompatible
fixes that are unavailable to 2.x users.


2.7 is where a new version of 2to3 will be distributed.  As people 
actually start trying to migrate real-world code, lots of issues are 
inevitably going to be discovered there.  From my perspective, 2.7 and 
3.1 need to be synced because 2.7 is the tool that will actually enable 
users of existing code to *use* 3.1.


And this isn't just about a release of the 2to3 tool itself, but fixes 
in the 2.x backports of various stdlib features to deal with the kinds 
of parity issues that users are only going to discover in large-scale, 
real-world testing.

___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] Save file by using file() function and fileDialog()

2008-10-29 Thread Sonia

 
I m using fileDialog(self, message, path, filename, filter, aStyle(opotional)) 
to save the file. 
In my code, i used fileDialog to show save dialog box and when we click on save 
button, it should save that file which is of txt type (filter = '*.txt'). But 
when we click on save button it returns error: "coercing to unicode: need 
string or buffer, list found" rather than saving / creating a file. I also 
tried f = file(myfile, 'w', 1000) instead of f = file(myfile, 'w'), where 1000 
is buffer size, but both have the same error. where as if we use 




file(
filename[, mode[, bufsize]])
, then it creates a file of specified type. But it is not working in 
fileDialog(). Why?Where i m wrong?
 
What should i do?
 
Following is my code:
def on_btn2_mouseClick(self, event):aStyle = 
wx.SAVE|wx.HIDE_READONLY|wx.OVERWRITE_PROMPTfilter = '*.txt'
result = dialog.fileDialog(self, 'ist def', '', 'n', wildcard, aStyle)  
  myfile= result.pathsif result.accepted == True :f = 
file(myfile, 'w')f.write('my file')f.close()
_
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com