Barry Scott wrote:
I recursive grep'ed and missed this ref. However I did read this in
README.TXT:
> Building on non-UNIX systems
>
> For Windows (2000/NT/ME/98/95), assuming you have MS VC++ 6.0, the
> project files are in PCbuild, the workspace is pcbuild.dsw.
On Thu, Dec 23, 2004 at 09:41:20PM +1000, Nick Coghlan wrote:
> I just spent 10 minutes hunting through the Python website for this link:
> http://www.python.org/doc/newstyle.html
>
> I knew it was there somewhere, I just couldn't find the darn thing.
>
> It turns out the major mistake I made was
Barry Scott <[EMAIL PROTECTED]> writes:
> I recursive grep'ed and missed this ref. However I did read this in
> README.TXT:
The top-level README file is hilariously out-of-date, in some ways. I
meant to do something about this before 2.4 final, but didn't get
around to it...
Cheers,
mwh
--
Hi,
On Fri, Dec 24, 2004 at 12:17:49AM +, Barry Scott wrote:
> I recursive grep'ed and missed this ref. However I did read this in
> README.TXT:
The "extending and embedding" tutorial is similarily out-of-date.
Armin
___
Python-Dev mailing list
P
Armin Rigo <[EMAIL PROTECTED]> writes:
> Hi,
>
> On Fri, Dec 24, 2004 at 12:17:49AM +, Barry Scott wrote:
>> I recursive grep'ed and missed this ref. However I did read this in
>> README.TXT:
>
> The "extending and embedding" tutorial is similarily out-of-date.
Well, I've half re-written tha
I'm about to travel to a place where I don't expect to have internet
access for over a week, so this is my last message in 2004. I'll have
more time next year for Python that I had this year, so I'm looking
forward to working again with this great community. I wish everyone
happy celebrations of th
After implementing over 10 new opcodes for my thesis I figured I should write
down the basic steps in an info PEP so that there is enough guidelines with
this PEP and PEP 306 to cover the bases on changes to the language itself.
To go along with this I also plan to write some benchmarks for indi
Brett C. wrote:
A few things can be done to make sure that development goes smoothly when
experimenting with Python's bytecode. One is to delete all .py(c|o|w)
Don't you mean ".pyc or .pyo (remember such files in zips as well)"
.pyw is normal python source.
-- Scott David Daniels
[EMAIL PROTECTED
"Brett C." <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
At to the title, bytecodes are a property of the CPython implementation,
not of Python itself. Since I think the distinction is quite important to
maintain, I would insert the missing 'C' and everywhere else as
appropriat
