Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #11224 > unrolled thread

Re: code object differences between 2.7 and 3.3a

Started byNed Deily <nad@acm.org>
First post2011-08-11 10:26 -0700
Last post2011-08-11 10:26 -0700
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.


Contents

  Re: code object differences between 2.7 and 3.3a Ned Deily <nad@acm.org> - 2011-08-11 10:26 -0700

#11224 — Re: code object differences between 2.7 and 3.3a

FromNed Deily <nad@acm.org>
Date2011-08-11 10:26 -0700
SubjectRe: code object differences between 2.7 and 3.3a
Message-ID<mailman.2186.1313083662.1164.python-list@python.org>
In article 
<CALFfu7BZoxttcgULpmrmiV4UMBCos7joUm8bRZXxQ+N25t4RrA@mail.gmail.com>,
 Eric Snow <ericsnowcurrently@gmail.com> wrote:
> Specifically, I am wondering why there is a difference for co_names.

This is not an answer to your question but, as a metapoint, in my 
experience it is usually faster and often more reliable to try to answer 
questions like this yourself using the tools that the Python project 
provides:

- clone a copy of the hg repository and update to the branch of interest

- become familiar with the code layout (the developers guide can help 
with this (http://docs.python.org/devguide/)

- use "hg annotate" to see what lines were changed by what rev sets and 
by whom

- use "hg log -v <filename>" to browse the history entries for the file 

- look up the tracker issues referenced in those history entries and 
follow the discussions there

The Python project has an effective process for code development and one 
that emphasizes good documentation of changes and additions.  For 
instance, as part of the transition earlier this year from Subversion to 
Mercurial, great care was taken to preserve as much of the existing 
source history as possible going far back into the time machine.  It's 
to your advantage to take advantage of these sources of history.

-- 
 Ned Deily,
 nad@acm.org

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web