pyallegro-general — General Python-Allegro-stuff

Re: [Pyallegro] Switching to SVN?

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

>     Subversion Server:  https://svn.sourceforge.net
>     Path to Repository: /svnroot/pyallegro
> 
> I wonder about the /svnroot/ part, since you already access
> svn.sourceforge.net...

So they are using https and wonder about poor SVN
performance... anyway, the import is done I believe the first
thing should be to reorganise the hiearchy. Since both projects
are different, instead of the typical branch-trunk-tag/project we
could move it to project/branch-trunk-tag.

Is that ok?

Re: [Pyallegro] Switching to SVN?

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

On 2006-03-13, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> I'll request the SVN repository soon (SF is down due to maintenance).

Done. Automatic migration of the current CVS
repository is pending. SF docs about SVN are at:
http://sourceforge.net/docs/E09. Apparently the most interesting
stuff is:

    Subversion Server:  https://svn.sourceforge.net
    Path to Repository: /svnroot/pyallegro

I wonder about the /svnroot/ part, since you already access
svn.sourceforge.net...

Re: [Pyallegro] Switching to SVN?

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

On 2006-03-13, AKX <th...@gm...> wrote:
> Just noticed this message, and I'm really thumbs up for SVN.

I'll request the SVN repository soon (SF is down due to maintenance).

Re: [Pyallegro] Switching to SVN?

[AKX <th...@gm...>]

Just noticed this message, and I'm really thumbs up for SVN.

~ AKX.

On 3/12/06, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> Hey. How about switching the repositories to SVN? This doesn't
> imply CVS is going to be dropped, since SF offers having both.
> If you are happy with CVS you could keep using it.

[Pyallegro] Switching to SVN?

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

Hey. How about switching the repositories to SVN? This doesn't
imply CVS is going to be dropped, since SF offers having both.
If you are happy with CVS you could keep using it.

Re: [Pyallegro] PyAlleg + Linux, take two

[AKX <th...@gm...>]

Yes... so just really minor problems. VERY NICE, if I say it myself.
And thanks for that "Most of your examples are really pretty." :)

Blipchain has a couple of variables that can be changed. Lineofsight
isn't pixel perfect, but that's a matter of tuning again. That
bitmap.. ok, sorry, I'm on Windows. :P

Gotta go WoW now.

AKX

On 12/20/05, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> On 2005-12-20, AKX <th...@gm...> wrote:
> > Did you try all the tests?
>
> blipchain is terribly slow. lineofsight doesn't seem to be pixel
> perfect. test_load doesn't work because the smiley.bmp file is
> commited as smiley.BMP. test_mandel.py is mentioned twice in
> readme.html.  nodes.py suffers from 2.4 versionitis. fillers.py
> fails with:
>
> >9
> SumSortBadfill
> Traceback (most recent call last):
>   File "fillers.py", line 159, in ?
>     bf.do()
>   File "fillers.py", line 24, in do
>     p=3Dself.selectNode()
>   File "fillers.py", line 89, in selectNode
>     self.n.sort(None,sum)
> TypeError: sort expected at most 1 arguments, got 2
>
> Most of your examples are really pretty.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Pyallegro-general mailing list
> Pya...@li...
> https://lists.sourceforge.net/lists/listinfo/pyallegro-general
>

Re: [Pyallegro] PyAlleg-Pyrex 0.1.3.6 released

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

On 2005-12-20, AKX <th...@gm...> wrote:
> I released 0.1.3.6b of PyAlleg-Pyrex.
> I'm waiting for the flames, ducks and manhole covers now. (Now, wasn't
> that obscure?)

Too much for me. End users might benefit from a web page link to it.

Re: [Pyallegro] PyAlleg + Linux, take two

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

On 2005-12-20, AKX <th...@gm...> wrote:
> Did you try all the tests?

blipchain is terribly slow. lineofsight doesn't seem to be pixel
perfect. test_load doesn't work because the smiley.bmp file is
commited as smiley.BMP. test_mandel.py is mentioned twice in
readme.html.  nodes.py suffers from 2.4 versionitis. fillers.py
fails with:

>9
SumSortBadfill
Traceback (most recent call last):
  File "fillers.py", line 159, in ?
    bf.do()
  File "fillers.py", line 24, in do
    p=self.selectNode()
  File "fillers.py", line 89, in selectNode
    self.n.sort(None,sum)
TypeError: sort expected at most 1 arguments, got 2

Most of your examples are really pretty.

[Pyallegro] PyAlleg-Pyrex 0.1.3.6 released

[AKX <th...@gm...>]

I released 0.1.3.6b of PyAlleg-Pyrex.
I'm waiting for the flames, ducks and manhole covers now. (Now, wasn't
that obscure?)

AKX

Re: [Pyallegro] PyAlleg + Linux, take two

[AKX <th...@gm...>]

Well, there are no other 2.4 dependent parts. And actually, due to
that fix, there are NO 2.4 _dependent_ parts. The events module will
just be somewhat slower.

Did you try all the tests?

On 12/19/05, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> On 2005-12-19, AKX <th...@gm...> wrote:
> > Committed fix to pyalleg_events.py.  Set() is a Python
> > 2.4 built-in, but thankfully, there is the sets module
> > for... lesser... Pythons.
>
> Requiring a specific version of python or pyrex is not a problem
> as long as you can detect that in the build script and show a big
> warning for your users.
>
> test_show.py is pretty, runs at 15fps on my PIII 800Mhz. Now you
> only need to pack that, upload to sourceforge and maybe announce
> it on freshmeat to profit.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Pyallegro-general mailing list
> Pya...@li...
> https://lists.sourceforge.net/lists/listinfo/pyallegro-general
>

[Pyallegro] est

[<in...@lo...>]

.

Re: [Pyallegro] PyAlleg + Linux, take two

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

On 2005-12-19, AKX <th...@gm...> wrote:
> Committed fix to pyalleg_events.py.  Set() is a Python
> 2.4 built-in, but thankfully, there is the sets module
> for... lesser... Pythons.

Requiring a specific version of python or pyrex is not a problem
as long as you can detect that in the build script and show a big
warning for your users.

test_show.py is pretty, runs at 15fps on my PIII 800Mhz. Now you
only need to pack that, upload to sourceforge and maybe announce
it on freshmeat to profit.

Re: [Pyallegro] PyAlleg + Linux, take two

[AKX <th...@gm...>]

Committed fix to pyalleg_events.py.
Set() is a Python 2.4 built-in, but thankfully, there is the sets
module for... lesser... Pythons.

AKX

On 12/18/05, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> On 2005-12-18, AKX <th...@gm...> wrote:
> > I made a couple of commits and now it does WORK under a VMware Debian
> > installation.
> > Could you try it out?
>
> It compiles and installs, but running any of the tests gives out:
>
> [1:gradha@noir:0] [~/project/python/pyalleg-pyrex/tests]$ python test_loa=
d.py
> Traceback (most recent call last):
>   File "test_load.py", line 1, in ?
>     from pyalleg import *
>   File "/usr/lib/python2.3/site-packages/pyalleg/__init__.py", line 15, i=
n ?
>     import pyalleg_events as events
>   File "/usr/lib/python2.3/site-packages/pyalleg/pyalleg_events.py", line=
 7, in ?
>     keysDown=3Dset()
> NameError: name 'set' is not defined
>
> Maybe it requires a special version of python/pyrex? I have 2.3.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Pyallegro-general mailing list
> Pya...@li...
> https://lists.sourceforge.net/lists/listinfo/pyallegro-general
>

Re: [Pyallegro] PyAlleg + Linux, take two

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

On 2005-12-18, AKX <th...@gm...> wrote:
> I made a couple of commits and now it does WORK under a VMware Debian
> installation.
> Could you try it out?

It compiles and installs, but running any of the tests gives out:

[1:gradha@noir:0] [~/project/python/pyalleg-pyrex/tests]$ python test_load.py   
Traceback (most recent call last):
  File "test_load.py", line 1, in ?
    from pyalleg import *
  File "/usr/lib/python2.3/site-packages/pyalleg/__init__.py", line 15, in ?
    import pyalleg_events as events
  File "/usr/lib/python2.3/site-packages/pyalleg/pyalleg_events.py", line 7, in ?
    keysDown=set()
NameError: name 'set' is not defined

Maybe it requires a special version of python/pyrex? I have 2.3.

[Pyallegro] PyAlleg + Linux, take two

[AKX <th...@gm...>]

I made a couple of commits and now it does WORK under a VMware Debian
installation.
Could you try it out?

AKX

Re: [Pyallegro] Releasing alpy 0.1.2

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

On 2005-12-17, Grzegorz Adam Hankiewicz <gradha@localhost> wrote:
> I checked out and the build process failed with lots of errors
> I'm attaching.

Here...

Re: [Pyallegro] Releasing alpy 0.1.2

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

On 2005-11-20, AKX <th...@gm...> wrote:
> Well, I certainly have interest towards its usage, but I guess
> working on it is frozen for some time... unless someone else wants
> to do something with it. I'd appreciate it if someone tested it
> on Linux and other OSes, though.

I checked out and the build process failed with lots of errors
I'm attaching.  Anyway, you should release a snapshot as a file
for those too lazy to get stuff from CVS. You will see more bug
reports/interest then.

[Pyallegro] Reproducing an X deadlock

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

Hello there.

With the following simple test I get a deadlock under Linux/X. Can
somebody reproduce it? The same code in C works fine, so I guess
it's python doing evil things, and Allegro not being unevil enough.

 #!/usr/bin/env python
 
 import alpy
 
 def init_alpy():
         alpy.init()
         alpy.set_gfx_mode(alpy.GFX_AUTODETECT_WINDOWED, 640, 480)
         points = [(50, 50), (100, 100), (100, 150),(50, 200), (0, 150), (0, 100)]
         white = alpy.makecol(255, 255, 255)
         black = alpy.makecol(0, 0, 0)
         alpy.screen.clear(white)
         alpy.screen.polygon(points, black)
 
 init_alpy()

Re: [Pyallegro] Releasing alpy 0.1.2

[AKX <th...@gm...>]

Well, I certainly have interest towards its usage, but I guess working
on it is frozen for some time... unless someone else wants to do
something with it. I'd appreciate it if someone tested it on Linux and
other OSes, though.

AKX

On 11/20/05, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> On 2005-11-20, AKX <th...@gm...> wrote:
> > Well, you can just edit the HTML directly, there's no problem
> > with that. I'll just staticify the front page to make it easier
> > to hand-edit. ... There, done. You can just edit index.php to
> > edit the news now.
>
> Thanks, done. Now I guess it's time for you to do the same with the
> rexx version. Are you going to keep working on it or lost interest?
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
> _______________________________________________
> Pyallegro-general mailing list
> Pya...@li...
> https://lists.sourceforge.net/lists/listinfo/pyallegro-general
>

Re: [Pyallegro] Releasing alpy 0.1.2

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

On 2005-11-20, AKX <th...@gm...> wrote:
> Well, you can just edit the HTML directly, there's no problem
> with that. I'll just staticify the front page to make it easier
> to hand-edit. ... There, done. You can just edit index.php to
> edit the news now.

Thanks, done. Now I guess it's time for you to do the same with the
rexx version. Are you going to keep working on it or lost interest?

Re: [Pyallegro] Releasing alpy 0.1.2

[AKX <th...@gm...>]

Well, you can just edit the HTML directly, there's no problem with
that. I'll just staticify the front page to make it easier to
hand-edit. ... There, done. You can just edit index.php to edit the
news now.

On 11/19/05, Grzegorz Adam Hankiewicz <gr...@ti...> wrote:
> I'm releasing right now 0.1.2 on freshmeat. I was wondering what
> to do with our web. Things haven't magically improved, have they?
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
> _______________________________________________
> Pyallegro-general mailing list
> Pya...@li...
> https://lists.sourceforge.net/lists/listinfo/pyallegro-general
>

[Pyallegro] Releasing alpy 0.1.2

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

I'm releasing right now 0.1.2 on freshmeat. I was wondering what
to do with our web. Things haven't magically improved, have they?

Re: [Pyallegro] About the web page

[AKX <th...@gm...>]

> Hows your work going on the pyrexx version?

Well, I'll have to do some work on it -- I think the CVS version is
the most recent at the moment.
It even compiles on my school Mac OS X 10.2 machine (but trying to
init() crashes with a 'Bus error' - I blame 10.2, 10.3+ would probably
work better). An older version did work on Linux, but haven't tested
the most recent one. I think there may be some memory leaks around
bitmaps, maybe, not to mention that the "additional loaders"  (PNG
etc) are a horrid kludge. Oh well ;)

AKX.

Re: [Pyallegro] About the web page

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

On 2005-10-23, AKX <th...@gm...> wrote:
> Sigh, they've messed up sessions, so I can't get anything to work
> right now...

Don't worry, it's not like I was going to update the web right
now. Hows your work going on the pyrexx version?

Re: [Pyallegro] About the web page

[AKX <th...@gm...>]

Sigh, they've messed up sessions, so I can't get anything to work right now=
...