pyallegro-general — General Python-Allegro-stuff

Re: [Pyallegro] So how do I use that?

[Juha-Matti T. <jm...@pu...>]

On to, 2001-12-20 at 23:29, Grzegorz Adam Hankiewicz wrote:
> On Thu, Dec 20, 2001 at 10:19:49PM +0200, Juha-Matti Tapio wrote:
> > I had previously similar trouble, but I managed to get the stuff
> > installed when running setup as root. Could this problem be about this?
> Output/effect remains the same as root or user. Same messages with both
> python versions (1.5 and 2.1).

Just a thought. Do you have python-dev package installed?

Currently the cvs-version seems to build nicely with the newest 2.1 and
2.2 Debian packages.


-- 
Juha-Matti Tapio, ATK-suunnittelija, fil. yo.
+358-50-5419230

Re: [Pyallegro] So how do I use that?

[Grzegorz A. H. <gr...@te...>]

On Thu, Dec 20, 2001 at 10:19:49PM +0200, Juha-Matti Tapio wrote:
> I had previously similar trouble, but I managed to get the stuff
> installed when running setup as root. Could this problem be about this?

Output/effect remains the same as root or user. Same messages with both
python versions (1.5 and 2.1).

-- 
 Grzegorz Adam Hankiewicz   gr...@te...   http://gradha.infierno.org/

Re: [Pyallegro] So how do I use that?

[Juha-Matti T. <jm...@pu...>]

On ke, 2001-12-19 at 23:20, Grzegorz Adam Hankiewicz wrote:
> Ok, so I get those warnings both with python 1.5 and 2.1, which means that
> alpy won't be installed. However I can force to use it running python
> from that directory.  It doesn't work with 1.5 (hopefully this had been
> documented before I tried it), and 2.1 just gives a weird message and
> exists when I try to use allegro_init.

I had previously similar trouble, but I managed to get the stuff
installed when running setup as root. Could this problem be about this?

But there is something odd with the setup.py and/or distutils.

> ImportError: /usr/lib/python1.5/site-packages/_alpy.so: undefined symbol: PyObject_DEL

That's odd. I'll try to update my python debs and see if I can do
something about this.

Re: [Pyallegro] So how do I use that?

[Grzegorz A. H. <gr...@te...>]

On Fri, Dec 14, 2001 at 11:18:07PM +0100, Grzegorz Adam Hankiewicz wrote:
> I get some weird messages from setup.py:
> 
> [gregorio:69] [~/cvs/libs/pyallegro]$ ./setup.py install
> running install
> running build
> running build_py
> warning: build_py: file a.py (for module a) not found
> warning: build_py: file l.py (for module l) not found
> warning: build_py: file p.py (for module p) not found
> warning: build_py: file y.py (for module y) not found
> warning: build_py: file a.py (for module a) not found
> warning: build_py: file l.py (for module l) not found
> warning: build_py: file p.py (for module p) not found
> warning: build_py: file y.py (for module y) not found
> running build_ext
> skipping '_alpy' extension (up-to-date)
> running install_lib
> not copying build/lib.linux-i686-1.5/_alpy.so (output up-to-date)

Ok, so I get those warnings both with python 1.5 and 2.1, which means that
alpy won't be installed. However I can force to use it running python
from that directory.  It doesn't work with 1.5 (hopefully this had been
documented before I tried it), and 2.1 just gives a weird message and
exists when I try to use allegro_init.

[gregorio:6] [~/cvs/libs/pyallegro]$ python
Python 1.5.2 (#0, Dec 27 2000, 13:59:38)  [GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
>>> import alpy
Traceback (innermost last):
  File "<stdin>", line 1, in ?
  File "alpy.py", line 23, in ?
    import _alpy, sys
ImportError: /usr/lib/python1.5/site-packages/_alpy.so: undefined symbol: PyObject_DEL

[gregorio:7] [~/cvs/libs/pyallegro]$ python2.1
Python 2.1.1 (#1, Aug 25 2001, 15:17:34)
[GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import alpy
>>> alpy.allegro_init()
>>> Temporizador
and here the interactive sesion ends.

-- 
 Grzegorz Adam Hankiewicz   gr...@te...   http://gradha.infierno.org/

[Pyallegro] So how do I use that?

[Grzegorz A. H. <gr...@te...>]

Hello.

I am trying to get something in python using allegro, but some things seem
to be broken. I tried running ./setup install, and I get some problems
compiling _alpymodule.c (patch attached to compile properly). Then,
I get some weird messages from setup.py:

[gregorio:69] [~/cvs/libs/pyallegro]$ ./setup.py install
running install
running build
running build_py
warning: build_py: file a.py (for module a) not found
warning: build_py: file l.py (for module l) not found
warning: build_py: file p.py (for module p) not found
warning: build_py: file y.py (for module y) not found
warning: build_py: file a.py (for module a) not found
warning: build_py: file l.py (for module l) not found
warning: build_py: file p.py (for module p) not found
warning: build_py: file y.py (for module y) not found
running build_ext
skipping '_alpy' extension (up-to-date)
running install_lib
not copying build/lib.linux-i686-1.5/_alpy.so (output up-to-date)

Any help with that?

-- 
 Grzegorz Adam Hankiewicz   gr...@te...   http://gradha.infierno.org/

Re: [Pyallegro] Little stupid patch

[Juha-Matti T. <jm...@pu...>]

On Mon, Dec 03, 2001 at 12:09:50AM +0100, Grzegorz Adam Hankiewicz wrote:
> I agree that this patch is not so useful anyway, but hey, we all have
> to start with something ;)

I think this is a useful patch since it updates pretty much the whole 
content of that file :)

Thanks anyway.

> BTW, AFAIC understand the MIT license is the same like giftware but
> without the "moral recommendation", right?

Pretty much yes. It's a quite neutral license. Though I'm considering the 
Allegro license.


-- 
Juha-Matti Tapio, ATK-suunnittelija, fil. yo.
+358-50-5419230

[Pyallegro] Little stupid patch

[Grzegorz A. H. <gr...@te...>]

Hi.

I agree that this patch is not so useful anyway, but hey, we all have
to start with something ;)

BTW, AFAIC understand the MIT license is the same like giftware but
without the "moral recommendation", right?

-- 
 Grzegorz Adam Hankiewicz   gr...@te...   http://gradha.infierno.org/