On Sun, Jul 22, 2012 at 8:55 PM, r.david.murray
wrote:
> http://hg.python.org/cpython/rev/80b81658455b
> changeset: 78246:80b81658455b
> parent: 78244:c43d73277756
> parent: 78245:b97f65f2298d
> user:R David Murray
> date:Sun Jul 22 21:53:54 2012 -0400
> summary:
>
On Sun, Jul 22, 2012 at 2:06 PM, Ezio Melotti wrote:
> On Sun, Jul 22, 2012 at 12:18 PM, anatoly techtonik
> wrote:
>> What is a print policy for deprecated modules? "new" module is
>> deprecated in 2.6, but 2.7.3 doesn't print any warnings. Is it a bug?
>> python -Wd -c "import new"
>
> In
On 22 July 2012 20:57, R. David Murray wrote:
> Benjamin sent me this message separately(*) privately and I responded
> privately. Here is my response.
>
(*) or his mailer did
>
I think I accidentally replied from my work email address (which is not
subscribed to python-dev) and so the second
On Sun, Jul 22, 2012 at 12:18 PM, anatoly techtonik wrote:
> What is a print policy for deprecated modules? "new" module is
> deprecated in 2.6, but 2.7.3 doesn't print any warnings. Is it a bug?
> python -Wd -c "import new"
In theory this should show a warning, but for some reason it doesn't
Benjamin sent me this message separately(*) privately and I responded
privately. Here is my response.
(*) or his mailer did
On Sun, 22 Jul 2012 20:22:50 +0100, Oscar Benjamin
wrote:
> On 22 July 2012 14:08, R. David Murray wrote:
>
> > On Sun, 22 Jul 2012 11:21:38 +0300, anatoly techtonik
> >
On 22 July 2012 14:08, R. David Murray wrote:
> On Sun, 22 Jul 2012 11:21:38 +0300, anatoly techtonik
> wrote:
> > http://docs.python.org/py3k/howto/pyporting.html#during-installation
> >
> > What's the point in making implicit Python 3 check here:
> > try: # Python 3
> > from distutils.comma
On Sun, 22 Jul 2012 20:39:15 +0300
Andrew Svetlov wrote:
> Ok.
> Sorry for my mistake — there are really no commits for
> http://bugs.python.org/issue15417
> It's look important for me — but you are release manager.
> If you consider the patch as potentially dangerous — I have to agree with you.
>
Ok.
Sorry for my mistake — there are really no commits for
http://bugs.python.org/issue15417
It's look important for me — but you are release manager.
If you consider the patch as potentially dangerous — I have to agree with you.
You are the master :)
On Sun, Jul 22, 2012 at 7:50 PM, Georg Brandl
On 07/22/2012 06:10 PM, Andrew Svetlov wrote:
> Georg, sorry, I've committed it before you answered.
After you wrote that you'd wait three days... anyway, I can't find the
commit in the repository, so that's fine.
> If you want, I will revert it back.
> But, please, describe me why those scripts
Georg, sorry, I've committed it before you answered.
If you want, I will revert it back.
But, please, describe me why those scripts are to late for 3.3?
I strongly checked correctness of both activation script for fish and
csh/tsch shells.
Works fine.
It's not *new feature*, it is just extending
These are new features, please do not commit before 3.3 is released.
Georg
On 07/22/2012 02:12 AM, Andrew Svetlov wrote:
> I created http://bugs.python.org/issue15417 with required activation scripts.
> If there are no objections I like to commit it after, say, three days.
>
> On Thu, Jul 19, 20
On Sun, 22 Jul 2012 11:21:38 +0300, anatoly techtonik
wrote:
> http://docs.python.org/py3k/howto/pyporting.html#during-installation
>
> What's the point in making implicit Python 3 check here:
> try: # Python 3
> from distutils.command.build_py import build_py_2to3 as build_py
> except Import
What is a print policy for deprecated modules? "new" module is
deprecated in 2.6, but 2.7.3 doesn't print any warnings. Is it a bug?
python -Wd -c "import new"
--
anatoly t.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mail
http://docs.python.org/py3k/howto/pyporting.html#during-installation
What's the point in making implicit Python 3 check here:
try: # Python 3
from distutils.command.build_py import build_py_2to3 as build_py
except ImportError: # Python 2
from distutils.command.build_py import build_py
inste
14 matches
Mail list logo
