Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #68446 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2014-03-18 05:08 +1100 |
| Last post | 2014-03-18 05:08 +1100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Thread._stop() behavior changed in Python 3.4 Chris Angelico <rosuav@gmail.com> - 2014-03-18 05:08 +1100
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-03-18 05:08 +1100 |
| Subject | Re: Thread._stop() behavior changed in Python 3.4 |
| Message-ID | <mailman.8213.1395079709.18130.python-list@python.org> |
On Tue, Mar 18, 2014 at 4:59 AM, Felix Yan <felixonmars@gmail.com> wrote: > For now I just skipped the test suites for paramiko to get the packaging done > (since the test suites themselves are passed without a problem, just the test > script made something wrong). I'll try to follow up the issue for paramiko :) I've posted comments on both the issues you linked to. My guess based on a cursory look at paramiko is that it's a test suite watchdog, which would be much better implemented with a subprocess; I may be wrong, though. In any case, if it's just a tests problem, you should theoretically be able to ignore it. ChrisA
Back to top | Article view | comp.lang.python
csiph-web