Roger Binns wrote:
> The Python 2.3 source shows the latter form being used almost
> exclusively so at some point someone changed a lot of code.
That's correct. I changed it for Python 3, for PEP 3123.
> It would seem that common practise, the examples and the documentation
> don't all match each
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
>> It would seem that common practise, the examples and the documentation
>> don't all match each other!
>
> I cannot parse this sentence.
Py2 source: Uses PyObject_HEAD_INIT
Py2 code compiled under Py3: Gives serious warning
On Tue, Nov 11, 2008 at 7:06 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> Why was the special case for None being "smaller" than all other
> objects in Python removed from Python 3.0 ? (see object.c in Py2.x)
>
It wasn't true in Python 2.5, either. Observe:
Cashew:~/pokersleuth/tracker$ pytho
When I try to install python-3.0rcN I get the following warning:
running install_egg_info
Writing /usr/local/lib/python3.0/lib-dynload/Python-3.0rc2-py3.0.egg-info
* Note: not installed as 'python'.
* Use 'make fullinstall' to install as 'python'.
* However, 'make fullinstall' is discouraged,
* a
No, no, no! *Eventually* Python 3.0 will just be "python". Until
then, it needs to be "python3.0".
Long agon, Red Hat installed Python 2 as "python2" instead of "python"
and it led to endless problems.
On Wed, Nov 12, 2008 at 12:46 PM, Smith-Rowland, Edward M
<[EMAIL PROTECTED]> wrote:
>
> When
> Obviously the Python 3 documentation and examples need to be updated.
I see - please submit a bug report.
> Also why not remove PyObject_HEAD_INIT from Python 3 headers so that if
> it is used then the compile fails?
It's still needed for non-var objects.
Regards,
Martin
_
On Fri, Nov 14, 2008 at 7:37 AM, Smith-Rowland, Edward M
<[EMAIL PROTECTED]> wrote:
> Thank you for your reply.
> I didn't mean to instigate or revive a problem ;-)
> I guess when python-3.* is python we'll have python-2.* installed.
>
> I guess I forsee a significant amount of time when we'll need
Guido van Rossum wrote:
No, no, no! *Eventually* Python 3.0 will just be "python". Until
then, it needs to be "python3.0".
I think you should consider changing the installation policy to
installing each file with its own pythonx.y name and alias exactly one,
the system default, as 'python'.
On Fri, Nov 14, 2008 at 9:48 AM, Terry Reedy <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
>>
>> No, no, no! *Eventually* Python 3.0 will just be "python". Until
>> then, it needs to be "python3.0".
>
> I think you should consider changing the installation policy to installing
> each file w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
>> Also why not remove PyObject_HEAD_INIT from Python 3 headers so that if
>> it is used then the compile fails?
>
> It's still needed for non-var objects.
Wouldn't a var object have PyVarObject_HEAD and a non-var object have
P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
>> Obviously the Python 3 documentation and examples need to be updated.
>
> I see - please submit a bug report.
Yet another site that wants another login to report bugs. So someone
else can report it.
Roger
-BEGIN PGP SI
Roger Binns wrote:
> Martin v. Löwis wrote:
>>> Also why not remove PyObject_HEAD_INIT from Python 3 headers so that if
>>> it is used then the compile fails?
>> It's still needed for non-var objects.
>
> Wouldn't a var object have PyVarObject_HEAD and a non-var object have
> PyObject_HEAD?
That'
> Currently on Windows, python3.0 is installed as just plain 'python'.
> This already causes problems when I want to choose 2.5 or 3.0. In my
> quick start list, I have two entries which both say "Python (command
> line)" with the *same* icon.
What is a quick start list, and how did you get Pyth
> Ah, Windows. Can you file a bug about this? I think only MvL can do
> something about this.
Not really. We don't install anything into a quick start list (see my
other message - I don't even know what that is). For other icons, I
can't do anything, either; my artistic abilities are zero.
Regard
On Fri, Nov 14, 2008 at 09:27:24PM +0100, "Martin v. L?wis" wrote:
> > Currently on Windows, python3.0 is installed as just plain 'python'.
> > This already causes problems when I want to choose 2.5 or 3.0. In my
> > quick start list, I have two entries which both say "Python (command
> > line)" w
>I think it's Windows Quick Launch bar:
>
> http://www.google.com/search?q=windows+quick+launch
> http://images.google.com/images?q=windows+quick+launch
I see. Then I still don't fully understand the problem.
Terry apparently had to add the Python command line to the
quick launch bar himself
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My confusion was because I though that the HEAD for the data structure
had to use the same corresponding HEAD_INIT in the type. So for
whatever reason the PyTypeObject is declared as a var object which is
why the var HEAD_INIT is needed.
It still loo
Roger Binns wrote:
Obviously the Python 3 documentation and examples need to be updated.
Also why not remove PyObject_HEAD_INIT from Python 3 headers so that if
it is used then the compile fails?
Is there some reason not to define PyObject_HEAD_INIT so
that it expands into the appropriate PyVa
Martin v. Löwis wrote:
Currently on Windows, python3.0 is installed as just plain 'python'.
This already causes problems when I want to choose 2.5 or 3.0. In my
quick start list, I have two entries which both say "Python (command
line)" with the *same* icon.
What is a quick start list, and ho
19 matches
Mail list logo
