Re: [Python-Dev] Forgotten Py3.0 change to remove Queue.empty() and Queue.full()
Yup, I'd need to remove support in multiprocessing too. On Mar 4, 2009 8:39pm, Tennessee Leeuwenburg wrote: Hi all, just FYI... sorry for any list pollution I went ahead and tried adding a warning to my local checkout. The test suite raised a DeprecationWarning -- it appears those methods are currently in use by other Lib code: test_multibytecodec_support test_multiprocessing /home/tjl/python3/lib/python3.1/queue.py:98: DeprecationWarning: Queue.empty() is deprecated, and won't be in 3.2. DeprecationWarning) /home/tjl/python3/lib/python3.1/queue.py:109: DeprecationWarning: Queue.full() is deprecated, and won't be in 3.2. DeprecationWarning) /home/tjl/python3/lib/python3.1/queue.py:98: DeprecationWarning: Queue.empty() is deprecated, and won't be in 3.2. DeprecationWarning) /home/tjl/python3/lib/python3.1/queue.py:109: DeprecationWarning: Queue.full() is deprecated, and won't be in 3.2. DeprecationWarning) test_mutants test_netrc test_nis Regards, -T On Thu, Mar 5, 2009 at 12:30 PM, Raymond Hettinger pyt...@rcn.com> wrote: Just noticed that the empty() and full() methods were still there. IIRC, we agreed to take them out (but leaving qsize() exposed). The docs entries and test cases were taken out, but the actual methods were accidentally left in. If so, the only thing to do is deprecate it in 3.1 for removal in 3.2. I recommend adding a warning to 3.0.2 and removing in 3.1. Waiting for more 3.x uptake doesn't serve our users well. IIRC, that was the rationale for cmp() removal in 3.0.1. Even in 2.x, these methods were documented as being unreliable and were removed from the 3.0 docs entirely. We discussed removing them and most of the work was done. Guido, any thoughts? Raymond ___ 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/tleeuwenburg%40gmail.com -- -- Tennessee Leeuwenburg http://myownhat.blogspot.com/ "Don't believe everything you think" ___ 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
Re: [Python-Dev] Tracker cleanup - Roundup hacking report :)
On Mar 5, 2009 12:17pm, "Daniel (ajax) Diniz" wrote: Hi, Here's a progress report on the "let's make the tracker a bit better" tasks. ...snip Slightly off topic Daniel, but if you see any multiprocessing bugs lurking out there, can you make me (jnoller) the assignee? jesse ___ 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
Re: [Python-Dev] [Python-3000] Backporting multiprocessing?
Maybe we should backport those handy pep8 threading names ... ... Ok maybe not. On Oct 22, 2008 9:02am, Christian Heimes <[EMAIL PROTECTED]> wrote: [EMAIL PROTECTED] wrote: I checked in the contents of my multiprocessing.tar file and opened issues #1 and #2. I added a setup.py, disabled recv_bytes_into for now and fixed lots of naming issues. The multiprocessing code is using the new names of the threading module (current_thread, is_alive etc.) but Python 2.5 just have the old names (currentThread, isAlive). $ python2.5 setup.py build_ext -i $ PYTHONPATH=Lib python2.5 Lib/test/test_multiprocessing.py == ERROR: test_connection (__main__.WithProcessesTestConnection) -- Traceback (most recent call last): File "Lib/test/test_multiprocessing.py", line 1220, in test_connection self.assertEqual(conn.recv_bytes_into(buffer), AttributeError: '_multiprocessing.Connection' object has no attribute 'recv_bytes_into' -- Ran 123 tests in 12.309s FAILED (errors=1) :) Christian ___ Python-3000 mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/jnoller%40gmail.com ___ 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
Re: [Python-Dev] Holding a Python Language Summit at PyCon
On Dec 6, 2008 5:42pm, Brett Cannon <[EMAIL PROTECTED]> wrote: On Thu, Dec 4, 2008 at 17:02, Frank Wierzbicki wrote: > On Thu, Dec 4, 2008 at 3:16 PM, Brett Cannon wrote: >> On Thu, Dec 4, 2008 at 12:05, Frank Wierzbicki wrote: >>> On Wed, Dec 3, 2008 at 10:31 AM, AM Kuchling wrote: 14:00 - 15:30 = Two tracks: Cross-implementation issues: What do the various VMs want/need from CPython to help with their implementations? * Marking CPython-specific tests in the test suite? * Getting an implementation agnostic test suite for the Python language? * Separating the language tests and the pure Python part of the stdlib into a separate project? (Or publish them as a separate package.) * Transition plans for 3.0? Champion needed. >>> I would like to champion this one. >>> >> >> I told AMK this a while back, but might as well make it more public; I >> am up for chairing as well. > Brett, > > Are you saying you've already called the cross-implementation champion > role? No, I am saying I had told AMK I was interested in championing the session. He chose you, and that's that. One less thing for me to worry about. =) > If so I'm happy to defer or co-chair. Your call. I will definitely be there representing CPython as best as I can, so I will be making noise regardless of whether I am standing in front of the room or not. -Brett Is heckling covered as an official obligation? :) -jesse ___ 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
