headers
Zaur Shibzoukhov | 2 Dec 11:41
Picon

Pickle 3 and keyword arguments in __new__ after *

This is a case:

class C(object):
    def __new__(cls, *, b):
        inst = super().__new__(cls)
        inst.b = b
        return inst

>>> c = C(b=17)
>>> image = pickle.dumps(c, protocol=3)
>>> c = pickle.loads(image)
Traceback (most recent call last):
  File "test_new.py", line 17, in <module>
    c = pickle.loads(image)
  File "D:\Python30\lib\pickle.py", line 1329, in loads
    return Unpickler(file, encoding=encoding, errors=errors).load()
TypeError: __new__() needs keyword-only argument b

Do we need to improve pickle protocol in order to allow instance
creation functions get keyword arguments too?

Best regards,
Zaur
Permalink | Reply | 501 comments |
headers
Amaury Forgeot d'Arc | 2 Dec 14:10
Picon

Re: Pickle 3 and keyword arguments in __new__ after *

Hello,

Zaur Shibzoukhov wrote:
> This is a case:
>
> class C(object):
>    def __new__(cls, *, b):
>        inst = super().__new__(cls)
>        inst.b = b
>        return inst
>
>>>> c = C(b=17)
>>>> image = pickle.dumps(c, protocol=3)
>>>> c = pickle.loads(image)
> Traceback (most recent call last):
>  File "test_new.py", line 17, in <module>
>    c = pickle.loads(image)
>  File "D:\Python30\lib\pickle.py", line 1329, in loads
>    return Unpickler(file, encoding=encoding, errors=errors).load()
> TypeError: __new__() needs keyword-only argument b
>
> Do we need to improve pickle protocol in order to allow instance
> creation functions get keyword arguments too?

Note that you have a similar error even when the argument is a regular one:

class C(object):
   def __new__(cls, b):
       inst = super().__new__(cls)
       inst.b = b
(Continue reading)

Permalink | Reply | 501 comments |
headers
Suraj Barkale | 2 Dec 16:23
Gravatar

Re: 2.6.1 and 3.0

Christian Heimes <lists <at> cheimes.de> writes:

> 
> Giovanni Bajo wrote:
> > On mer, 2008-11-26 at 21:03 +0100, "Martin v. Löwis" wrote:
> > 
> >>> I'm sure the 
> >>> Python Software Foundation would easily get a free license of one of the 
> >>> good commercial MSI installer generators.
> >> Can you recommend a specific one?
> > 
> > I've had good results with Advanced Installer:
> > http://www.advancedinstaller.com/feats-list.html
> > 
> 
> The free edition is missing at least one important feature:
> 
> Merge Modules into your installation
> Create self-contained MSI packages, by including and configuring the 
> required merge modules.
> 
I would suggest using WiX Toolset (http://wix.sourceforge.net/) as it is open
source and supports almost all features of "Advanced Installer". AFAIK the
Visual Studio & MS Office teams use WiX for their installers. It also relies on
XML files to specify the MSI content.

Regards,
Suraj

_______________________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Barry Warsaw | 2 Dec 21:31
Favicon

Tomorrow's releases


I believe we are on track for releasing Python 3.0 final and 2.6.1  
tomorrow.  There is just one release blocker for 3.0 left -- Guido  
needs to finish the What's New for 3.0.

This is bug 2306.

So that Martin can have something to work with when he wakes up  
tomorrow morning, I would like to tag and branch the tree some time  
today, Tuesday 02-Dec US/Eastern.  Therefore I am freezing both the  
2.6 and 3.0 trees, with special dispensation to Guido for the updated  
What's New.

Ping me on irc @ freenode #python-dev if you have anything else to  
check in to either tree before then.  As soon as I hear from Guido, or  
issue 2306 is closed, I'm branching 3.0 and tagging it for release.

Great work everyone, we're almost there!
-Barry
Permalink | Reply | 0 comments |
headers
Barry Warsaw | 4 Dec 02:51
Favicon

RELEASED Python 3.0 final


On behalf of the Python development team and the Python community, I  
am happy to announce the release of Python 3.0 final.

Python 3.0 (a.k.a. "Python 3000" or "Py3k") represents a major  
milestone in Python's history, and was nearly three years in the  
making.  This is a new version of the language that is incompatible  
with the 2.x line of releases, while remaining true to BDFL Guido van  
Rossum's vision.  Some things you will notice include:

* Fixes to many old language warts
* Removal of long deprecated features and redundant syntax
* Improvements in, and a reorganization of, the standard library
* Changes to the details of how built-in objects like strings and  
dicts work
* ...and many more new features

While these changes were made without concern for backward  
compatibility, Python 3.0 still remains very much "Pythonic".

We are confident that Python 3.0 is of the same high quality as our  
previous releases, such as the recently announced Python 2.6.  We will  
continue to support and develop both Python 3 and Python 2 for the  
foreseeable future, and you can safely choose either version (or both)  
to use in your projects.  Which you choose depends on your own needs  
and the availability of third-party packages that you depend on.  Some  
other things to consider:

* Python 3 has a single Unicode string type; there are no more 8-bit  
strings
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dotan Cohen | 4 Dec 03:08
Picon
Gravatar

Re: RELEASED Python 3.0 final

2008/12/4 Barry Warsaw <barry <at> python.org>:
> On behalf of the Python development team and the Python community, I am
> happy to announce the release of Python 3.0 final.
>

Congratulations!

I have been learning Python 2.x while paying strict attention to the
3.x [in]compatibility issue. So, I have been waiting for this day
since I've started with Python!

--

-- 
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il

א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת
ا-ب-ت-ث-ج-ح-خ-د-ذ-ر-ز-س-ش-ص-ض-ط-ظ-ع-غ-ف-ق-ك-ل-م-ن-ه‍-و-ي
А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я
а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я
ä-ö-ü-ß-Ä-Ö-Ü
--
http://mail.python.org/mailman/listinfo/python-list
Permalink | Reply | 0 comments |
headers
Dotan Cohen | 4 Dec 03:13
Picon
Gravatar

Re: RELEASED Python 3.0 final

On this page:
http://www.python.org/download/releases/3.0/

The text "This is a proeuction release" should probably read "This is
a production release". It would give a better first impression :)

--

-- 
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il

א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת
ا-ب-ت-ث-ج-ح-خ-د-ذ-ر-ز-س-ش-ص-ض-ط-ظ-ع-غ-ف-ق-ك-ل-م-ن-ه‍-و-ي
А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я
а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я
ä-ö-ü-ß-Ä-Ö-Ü
--
http://mail.python.org/mailman/listinfo/python-list
Permalink | Reply | 0 comments |
headers
Barry Warsaw | 4 Dec 03:24
Favicon

Re: RELEASED Python 3.0 final


On Dec 3, 2008, at 9:13 PM, Dotan Cohen wrote:

> On this page:
> http://www.python.org/download/releases/3.0/
>
> The text "This is a proeuction release" should probably read "This is
> a production release". It would give a better first impression :)

Fixed, thanks!
-Barry
Permalink | Reply | 0 comments |
headers
Ed Leafe | 4 Dec 04:29
Favicon
Gravatar

Re: RELEASED Python 3.0 final

On Dec 3, 2008, at 7:51 PM, Barry Warsaw wrote:

> On behalf of the Python development team and the Python community, I  
> am happy to announce the release of Python 3.0 final.

	Props to all the folks whose hard work made this possible! You guys  
rock!

-- Ed Leafe

--
http://mail.python.org/mailman/listinfo/python-list
Permalink | Reply | 0 comments |
headers
Martin v. Löwis | 4 Dec 08:36
Picon
Gravatar

Merging mailing lists

I would like to merge mailing lists, now that the design and first
implementation of Python 3000 is complete. In particular, I would
like to merge the python-3000 mailing list back into python-dev,
and the python-3000-checkins mailing list back into python-checkins.
The rationale is to simplify usage of the lists, and to avoid
cross-postings.

To implement this, all subscribers of the 3000 mailing lists would
be added to the trunk mailing lists (avoiding duplicates, of course),
and all automated messages going to python-3000-checkins would then
be directed to the trunk lists. The 3000 mailing lists would change
into read-only mode (i.e. primarily leaving the archives behind).

Any objections?

Regards,
Martin
Permalink | Reply | 0 comments |

Gmane