Hello all,
I am working on a Python book, since it could be completed in about a
year (writing time + edition + publishing) or more, I would like to
know what version to target since I don't want to release a book that
will be outdated just after is printed.
I use 2.4 for everyday work but most we
> In article <[EMAIL PROTECTED]>,
>> crystalattice <[EMAIL PROTECTED]> wrote:
>>
>>> From: "Sebastian Bassi" <[EMAIL PROTECTED]>
>>> Date: Thurs, Aug 31 2006 7:51 am
>>> Subject: Re: Timeline for Python?
>>> Gr
wesley chun wrote:
> i cover through 2.5, but also include stuff that have
> already been slated for 2.6 and 2.7.
and what would that be? target versions in the PEP:s are usually just
wild guesses...
--
http://mail.python.org/mailman/listinfo/python-list
wesley chun wrote:
>
> 1. never write against older versions of Python... you will only
> obsolete your book even faster (well, "sooner")
I believe there is some market for documentation of older
versions of software. Many installations are constrained
by the cost of upgrading and can not mi
In message <[EMAIL PROTECTED]>, Blair P.
Houghton wrote:
> wesley chun wrote:
>>
>> 1. never write against older versions of Python... you will only
>> obsolete your book even faster (well, "sooner")
>
> I believe there is some market for documentation of older
> versions of software. Many i
Lawrence D'Oliveiro wrote:
>> I believe there is some market for documentation of older
>> versions of software. Many installations are constrained
>> by the cost of upgrading and can not migrate to a newer
>> version.
>
> And they can afford to buy books??
>
> If they're that strapped for cash
Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Blair P.
> Houghton wrote:
>
> > wesley chun wrote:
> >>
> >> 1. never write against older versions of Python... you will only
> >> obsolete your book even faster (well, "sooner")
> >
> > I believe there is some market for documentat
In article <[EMAIL PROTECTED]>,
Blair P. Houghton <[EMAIL PROTECTED]> wrote:
>wesley chun wrote:
>>
>> 1. never write against older versions of Python... you will only
>> obsolete your book even faster (well, "sooner")
>
>I believe there is some market for documentation of older versions of
>so
Aahz wrote:
> You did see my advice, seconded by Wes, that any book should cover the
> version differences? How is that sufficiently inadequate that new books
> should specifically target older versions?
I think it's a good idea, but I also think that it may cause authors to
rely on the old docu
> From: Fredrik Lundh <[EMAIL PROTECTED]>
> Date: Sat, Sep 23 2006 12:03 pm
>
>> i cover through 2.5, but also include stuff that have
>> already been slated for 2.6 and 2.7.
>
> and what would that be? target versions in the PEP:s are usually just
> wild guesses...
true, and it's obviously a *b
Sebastian Bassi wrote:
> So, if the book is published in October 2007, should feature Python 3
> or Python 2.5?
> I did read http://www.python.org/dev/peps/pep-3000/ but I still not
> sure about timeline.
I get the impression that Python 3 will not be around Any Time Soon and
certainly not in just
I'd write for 2.4, even though 2.5 should be coming out "shortly".
There aren't many significant changes to the whole language between 2.4
and 2.5. Probably the best thing is write for 2.4 and have a sidenote
stating where 2.5 operates differently.
The Python 3 timeline is almost a moving target
On 1 Sep 2006 00:57:04 -0700, crystalattice <[EMAIL PROTECTED]> wrote:
> I'd write for 2.4, even though 2.5 should be coming out "shortly".
> There aren't many significant changes to the whole language between 2.4
> and 2.5. Probably the best thing is write for 2.4 and have a sidenote
> stating wh
Sebastian Bassi wrote:
> Maybe I forgot to tell, but its going to take me at least 6 month to
> finish the book
I don't think anyone will know exactly how 3.0 will look within 6
months. Not that your publisher may care about that; there are plenty
of books out there that describe how the autho
In article <[EMAIL PROTECTED]>,
crystalattice <[EMAIL PROTECTED]> wrote:
>
>I'd write for 2.4, even though 2.5 should be coming out "shortly".
>There aren't many significant changes to the whole language between 2.4
>and 2.5. Probably the best thing is write for 2.4 and have a sidenote
>stating wh
Sebastian Bassi wrote:
> Hello all,
>
> I am working on a Python book, since it could be completed in about a
> year (writing time + edition + publishing) or more, I would like to
> know what version to target since I don't want to release a book that
> will be outdated just after is printed.
> I u
crystalattice wrote:
> I'd write for 2.4, even though 2.5 should be coming out "shortly".
> There aren't many significant changes to the whole language between 2.4
> and 2.5. Probably the best thing is write for 2.4 and have a sidenote
> stating where 2.5 operates differently.
Python in a Nutshe
17 matches
Mail list logo