-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failures with Python 3.3 #1008
Comments
From Dmitry Shachnev on 2012-10-25 15:10:05+00:00 This bug is also a big problem for Debian/Ubuntu as we are switching to Python 3.3 by default now. |
From Dmitry Shachnev on 2012-10-26 13:22:41+00:00 I've been trying to debug this, the only issue I can find the reason to fail is: [this check](https://github.com/sphinx-doc/testing/blob/5b9f431fc92fc76c01fcb3b86c02c37298f1c2fc/sphinx/util/__init__.py#L200 now) always returns Other issues are (I've no clue what may cause them):
|
From Takayuki Shimizukawa on 2012-10-30 01:11:07+00:00 I confirmed your reported test error with:
tested by:
sometime caused test error but sometime passed. I'm confusing.. BTW, I fixed a few errors.
I'll continue to fix. |
From Dmitry Shachnev on 2012-10-30 09:33:59+00:00 Thanks! Note that some issues can be fixed by patch from issue #998. |
From Takayuki Shimizukawa on 2012-10-30 13:26:11+00:00 I found error reason, but I don't know why working before Python-3.3...Dmitry, please change your code and test again.
|
From Dmitry Shachnev on 2012-10-30 16:48:24+00:00 Takayuki Shimizukawa: After that change, everything works! Thanks very much! Can you please commit it and propose a pull request? |
From Takayuki Shimizukawa on 2012-10-31 04:31:24+00:00 Dmitry Shachnev: Thanks for your confirmation! I sent PR83. |
From Georg Brandl on 2012-11-01 16:54:57+00:00 fix #1008: can't get correct source code filename because all modules have 'loader' attribute at Python-3.3. → <> |
5 tests fail with Python 3.3. I use Docutils trunk and Sphinx trunk.
Output of tests in attachment.
The text was updated successfully, but these errors were encountered: