[issue6837] Mark the compiler package as deprecated

Benjamin Peterson added the comment: Promoted warning to full DeprecationWarning in r79078. -- resolution: -> accepted status: open -> closed ___ Python tracker ___

[issue6837] Mark the compiler package as deprecated

Georg Brandl added the comment: +1. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue6837] Mark the compiler package as deprecated

Changes by Brett Cannon : -- priority: normal -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6837] Mark the compiler package as deprecated

Ezio Melotti added the comment: This can be reconsidered now that the DeprecationWarnings are silenced by default (see #7319). -- nosy: +ezio.melotti priority: -> normal resolution: wont fix -> status: closed -> open ___ Python tracker

[issue6837] Mark the compiler package as deprecated

Georg Brandl added the comment: "Bugs are not fixed" is somewhat misleading -- I assume you're referring to bugs like the one I closed recently. Those are all bugs that have been in the compiler package for ages, and users that hit them know them or work around them. If a regression comes up, i

[issue6837] Mark the compiler package as deprecated

Jean-Paul Calderone added the comment: Oops. I wrote "In contract" in my previous message. I meant "In contrast". -- ___ Python tracker ___

[issue6837] Mark the compiler package as deprecated

Jean-Paul Calderone added the comment: Hi Georg, thanks for your comment. I'm not sure I fully understand, though. The compiler package is widely used, okay. So I suppose that means that the desire here is to make those users happy? But the compiler package is deprecated, and has known bugs

[issue6837] Mark the compiler package as deprecated

Georg Brandl added the comment: The compiler package is surprisingly often used; we already had complaints when (I think) 2.6 began emitting lots of new DeprecationWarnings, but for modules/APIs whose replacements was straightforward. Replacing usage of the compiler package is usually not strai

[issue6837] Mark the compiler package as deprecated

Jean-Paul Calderone added the comment: Bugs are no longer being fixed in the compiler package. To me, that says it should be regular-deprecated. People with no short term plans of switching to Python 3 will still want to avoid the compiler package. They should be told about the deprecation to

[issue6837] Mark the compiler package as deprecated

Brett Cannon added the comment: The package is not going to be removed from 2.x at this point since 2.7 will most likely be the last major release of the line. But it does have a Py3k warning which is good enough in this situation. -- nosy: +brett.cannon resolution: -> wont fix statu

[issue6837] Mark the compiler package as deprecated

Changes by Georg Brandl : -- assignee: -> benjamin.peterson nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list maili

[issue6837] Mark the compiler package as deprecated

New submission from Jean-Paul Calderone : According to http://docs.python.org/library/compiler.html, the compiler package is deprecated. However, importing the compiler package does not emit a deprecation warning. It should, to convey this information to people who are actually trying to use th