Re: [Python-Dev] Summary of Python tracker Issues

2017-07-01 Thread Serhiy Storchaka

30.06.17 19:09, Python tracker пише:

ACTIVITY SUMMARY (2017-06-23 - 2017-06-30)
Python tracker at http://bugs.python.org/

To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
   open6006 (-20)


Victor closed a half of hundred his issues.

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


Re: [Python-Dev] Summary of Python tracker Issues

2017-07-01 Thread Serhiy Storchaka

23.06.17 19:09, Python tracker пише:


ACTIVITY SUMMARY (2017-06-16 - 2017-06-23)
Python tracker at http://bugs.python.org/

To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
   open6026 ( -8)


Terry closed a third of hundred outdated IDLE issues.

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


Re: [Python-Dev] Summary of Python tracker Issues

2017-07-01 Thread Victor Stinner
Le 1 juil. 2017 10:18 AM, "Serhiy Storchaka"  a écrit :

Victor closed a half of hundred his issues.


Let me elaborate :-) I am still learning the new GitHub workflow, and it's
common that I forget to close issues after merging a change. I had many
issues that I forgot to update since we moved to GitHub.

I had also complex bugs splitted into small issues and it took time to fix
all branches and to wait for buildots to confirm that it's really fixed.

To finish, I closed a lot of issues that were older than 2 years because
the bug was fixed in the meanwhile in another issue, or just because I lost
track of the issue and also lost interest and I don't consider that the bug
or feature was worth it.

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


[Python-Dev] Lazy_loading to pickle/unpickle_pure?

2017-07-01 Thread Bhavishya
Hi,
I added lazy_loading in pickle.py.Here's some statistics if you consider
them of any importance:

1)Unpickle_pure:
Lazy -> unpickle_pure_python: Mean +- std dev: 728 us +- 24 us

Original -> unpickle_pure_python: Mean +- std dev: 771 us +- 22 us

2)Pickle_pure:

Lazy-> pickle_pure_python: Mean +- std dev: 919 us +- 18 us

Orginal -> pickle_pure_python: Mean +- std dev: 1.04 ms +- 0.03 ms

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


Re: [Python-Dev] Lazy_loading to pickle/unpickle_pure?

2017-07-01 Thread Victor Stinner
What is lazy loading? How does it work?

Victor

Le 1 juil. 2017 6:02 PM, "Bhavishya"  a écrit :

> Hi,
> I added lazy_loading in pickle.py.Here's some statistics if you consider
> them of any importance:
>
> 1)Unpickle_pure:
> Lazy -> unpickle_pure_python: Mean +- std dev: 728 us +- 24 us
>
> Original -> unpickle_pure_python: Mean +- std dev: 771 us +- 22 us
>
> 2)Pickle_pure:
>
> Lazy-> pickle_pure_python: Mean +- std dev: 919 us +- 18 us
>
> Orginal -> pickle_pure_python: Mean +- std dev: 1.04 ms +- 0.03 ms
>
> Thanks
> bhavishya
>
>
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com