[Pyogp] pyogp, pjira, and svn

[Enus Linden]

The public jira has been updated to have Pyogp as a project against
which to log issues. I'd like to move toward using jira as the canonical
location where tasks and bugs are tracked. Once the trunk stabilizes
(this week I expect), the wiki will be updated with roadmap and status,
but jira will be where all the details live.

http://jira.secondlife.com/browse/PYO

Also, once the trunk stabilizes, I'd like to move toward a model of
developing in svn branches (thank you for starting this Tao), preserving
the trunk as much as possible as a place where we can assume code to run
as expected. As we get further along, we can talk about tagging, but
that's a longer term issue.

Thanks.

[Christian Scholz]

Hi!

Post by Enus Linden
The public jira has been updated to have Pyogp as a project against
which to log issues. I'd like to move toward using jira as the canonical
location where tasks and bugs are tracked. Once the trunk stabilizes
(this week I expect), the wiki will be updated with roadmap and status,
but jira will be where all the details live.

Thanks, Enus! :)

Post by Enus Linden
http://jira.secondlife.com/browse/PYO
Also, once the trunk stabilizes, I'd like to move toward a model of
developing in svn branches (thank you for starting this Tao), preserving
the trunk as much as possible as a place where we can assume code to run
as expected. As we get further along, we can talk about tagging, but
that's a longer term issue.

We should decide on a process for merging though. Right now I have 2
branches but are also blocked by those.

Does the new buildout now actually work for everybody?
I also added the requirement to install X-Code on a mac to the wiki. I
wanted to check out MinGW on Windows if this is what I need to make it
work there, too. If so I would also add instructions for windows to the
wiki).

Tomorrow I also want to clean up the buildout in that it uses the indra
packages and we can get rid of svn installs (So that windows users just
need TortoiseSVN but not a commandline svn, which I find painful as a
thought but anyway ;-) ).

Minimum Requirement for Python is 2.4 then which works for me. 2.3 has
no decorator support and @property is failing. For the libdev_mac
buildout Python 2.5 is required though (should be sufficient as it's for
uptodate macs with Python2.5 anyway).

I also hope a new setuptools release is out soon so we can get rid of
this buildout again as it's also a pain to update 2 buildout.cfg all the
time.

cheers,

Christian

[Meadhbh S. Hamrick (Infinity Linden)]

Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 486 bytes
Desc: This is a digitally signed message part
Url : http://lists.secondlife.com/pipermail/pyogp/attachments/20080722/e0075080/PGP.pgp

[Christian Scholz]

Hi!

The mac buildout is working fine for me, and i would definitely prefer
to have only one buildout system, but can I ask that we freeze the build
system for a few weeks? Moving to a new build system in the middle of
the OGP beta seems a touch risky. And we're talking about using a new
setuptools _with_ buildout, not eliminating buildout and doing
everything with setuptools, right?

buildout builds on top of setuptools and the problem we had was that the
existing release of it seems to have a bug (at least if subversion 1.5
is installed). What I did in libdev_mac was to checkout setuptools trunk
from svn, building an egg out of it (which is simply done by 'python
setup.py bdist_egg' with the egg ending up in dist/) and hardcoding this
egg to be used in the bootstrap process of the buildout (in this process
it usually downloads the latest release of setuptools and the latest
release of the buildout package which then gets started).

This of course is a workaround which I want to get rid of. Once Philip
Eby has done a new release I will revert the changes again and we are
back at a standard buildout.

So in fact, my plan is not to change the building process but simply to
get rid of this workaround (and use eggs instead of svn checkouts for
e.g. indra or eventlet).

I hope that clears things up, except cleanups no changes to the system
are planned.


-- Christian

-cheers
-m

Post by Christian Scholz
Hi!

Post by Enus Linden
The public jira has been updated to have Pyogp as a project against
which to log issues. I'd like to move toward using jira as the
canonical location where tasks and bugs are tracked. Once the trunk
stabilizes (this week I expect), the wiki will be updated with
roadmap and status, but jira will be where all the details live.

Thanks, Enus! :)

Post by Enus Linden
http://jira.secondlife.com/browse/PYO
Also, once the trunk stabilizes, I'd like to move toward a model of
developing in svn branches (thank you for starting this Tao),
preserving the trunk as much as possible as a place where we can
assume code to run as expected. As we get further along, we can talk
about tagging, but that's a longer term issue.

We should decide on a process for merging though. Right now I have 2
branches but are also blocked by those.
Does the new buildout now actually work for everybody?
I also added the requirement to install X-Code on a mac to the wiki. I
wanted to check out MinGW on Windows if this is what I need to make it
work there, too. If so I would also add instructions for windows to
the wiki).
Tomorrow I also want to clean up the buildout in that it uses the
indra packages and we can get rid of svn installs (So that windows
users just need TortoiseSVN but not a commandline svn, which I find
painful as a thought but anyway ;-) ).
Minimum Requirement for Python is 2.4 then which works for me. 2.3 has
buildout Python 2.5 is required though (should be sufficient as it's
for uptodate macs with Python2.5 anyway).
I also hope a new setuptools release is out soon so we can get rid of
this buildout again as it's also a pain to update 2 buildout.cfg all
the time.
cheers,
Christian
--
Christian Scholz video blog: http://comlounge.tv
COM.lounge blog: http://mrtopf.de/blog
Luetticher Strasse 10 Skype: HerrTopf
52064 Aachen Homepage: http://comlounge.net
Tel: [phone] E-Mail
Fax: [phone] IRC: MrTopf, Tao_T
neue Show: TOPFt?glich (http://mrtopf.de/blog/category/topf-taglich/)
_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

------------------------------------------------------------------------
_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

[Locklainn]

How hard would it be to have a single buildout (rather than 1 for mac
and 1 for PC)?

Post by Christian Scholz
Hi!

The mac buildout is working fine for me, and i would definitely
prefer to have only one buildout system, but can I ask that we freeze
the build system for a few weeks? Moving to a new build system in the
middle of the OGP beta seems a touch risky. And we're talking about
using a new setuptools _with_ buildout, not eliminating buildout and
doing everything with setuptools, right?

buildout builds on top of setuptools and the problem we had was that
the existing release of it seems to have a bug (at least if
subversion 1.5 is installed). What I did in libdev_mac was to checkout
setuptools trunk from svn, building an egg out of it (which is simply
done by 'python setup.py bdist_egg' with the egg ending up in dist/)
and hardcoding this egg to be used in the bootstrap process of the
buildout (in this process it usually downloads the latest release of
setuptools and the latest release of the buildout package which then
gets started).
This of course is a workaround which I want to get rid of. Once Philip
Eby has done a new release I will revert the changes again and we are
back at a standard buildout.
So in fact, my plan is not to change the building process but simply
to get rid of this workaround (and use eggs instead of svn checkouts
for e.g. indra or eventlet).
I hope that clears things up, except cleanups no changes to the system
are planned.
-- Christian

-cheers
-m

Post by Christian Scholz
Hi!

Post by Enus Linden
The public jira has been updated to have Pyogp as a project against
which to log issues. I'd like to move toward using jira as the
canonical location where tasks and bugs are tracked. Once the trunk
stabilizes (this week I expect), the wiki will be updated with
roadmap and status, but jira will be where all the details live.

Thanks, Enus! :)

Post by Enus Linden
http://jira.secondlife.com/browse/PYO
Also, once the trunk stabilizes, I'd like to move toward a model of
developing in svn branches (thank you for starting this Tao),
preserving the trunk as much as possible as a place where we can
assume code to run as expected. As we get further along, we can
talk about tagging, but that's a longer term issue.

We should decide on a process for merging though. Right now I have 2
branches but are also blocked by those.
Does the new buildout now actually work for everybody?
I also added the requirement to install X-Code on a mac to the wiki.
I wanted to check out MinGW on Windows if this is what I need to
make it work there, too. If so I would also add instructions for
windows to the wiki).
Tomorrow I also want to clean up the buildout in that it uses the
indra packages and we can get rid of svn installs (So that windows
users just need TortoiseSVN but not a commandline svn, which I find
painful as a thought but anyway ;-) ).
Minimum Requirement for Python is 2.4 then which works for me. 2.3
libdev_mac buildout Python 2.5 is required though (should be
sufficient as it's for uptodate macs with Python2.5 anyway).
I also hope a new setuptools release is out soon so we can get rid
of this buildout again as it's also a pain to update 2 buildout.cfg
all the time.
cheers,
Christian
--
http://comlounge.tv
http://mrtopf.de/blog
Luetticher Strasse 10 Skype: HerrTopf
http://comlounge.net
Tel: [phone] E-Mail
Fax: [phone] IRC: MrTopf, Tao_T
neue Show: TOPFt?glich (http://mrtopf.de/blog/category/topf-taglich/)
_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

------------------------------------------------------------------------
_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

[Christian Scholz]

Post by Locklainn
How hard would it be to have a single buildout (rather than 1 for mac
and 1 for PC)?

Once the release is out I would make it one again. Maybe the libdev_mac
also works under linux and windows. If so we can simply reference this.
But it only works with Python2.5. I would still would like to keep
python2.4 compatibility as well because some frameworks out there still
just run with 2.4 and I would like to enable those to use the lib as well.

Should I have some time I will experiment with the new buildout to maybe
detect the version and provide a setuptool egg for 2.4 as well.

-- Christian

Post by Locklainn

Post by Christian Scholz
Hi!

The mac buildout is working fine for me, and i would definitely
prefer to have only one buildout system, but can I ask that we freeze
the build system for a few weeks? Moving to a new build system in the
middle of the OGP beta seems a touch risky. And we're talking about
using a new setuptools _with_ buildout, not eliminating buildout and
doing everything with setuptools, right?

buildout builds on top of setuptools and the problem we had was that
the existing release of it seems to have a bug (at least if
subversion 1.5 is installed). What I did in libdev_mac was to checkout
setuptools trunk from svn, building an egg out of it (which is simply
done by 'python setup.py bdist_egg' with the egg ending up in dist/)
and hardcoding this egg to be used in the bootstrap process of the
buildout (in this process it usually downloads the latest release of
setuptools and the latest release of the buildout package which then
gets started).
This of course is a workaround which I want to get rid of. Once Philip
Eby has done a new release I will revert the changes again and we are
back at a standard buildout.
So in fact, my plan is not to change the building process but simply
to get rid of this workaround (and use eggs instead of svn checkouts
for e.g. indra or eventlet).
I hope that clears things up, except cleanups no changes to the system
are planned.
-- Christian

-cheers
-m

Post by Christian Scholz
Hi!

Post by Enus Linden
The public jira has been updated to have Pyogp as a project against
which to log issues. I'd like to move toward using jira as the
canonical location where tasks and bugs are tracked. Once the trunk
stabilizes (this week I expect), the wiki will be updated with
roadmap and status, but jira will be where all the details live.

Thanks, Enus! :)

Post by Enus Linden
http://jira.secondlife.com/browse/PYO
Also, once the trunk stabilizes, I'd like to move toward a model of
developing in svn branches (thank you for starting this Tao),
preserving the trunk as much as possible as a place where we can
assume code to run as expected. As we get further along, we can
talk about tagging, but that's a longer term issue.

We should decide on a process for merging though. Right now I have 2
branches but are also blocked by those.
Does the new buildout now actually work for everybody?
I also added the requirement to install X-Code on a mac to the wiki.
I wanted to check out MinGW on Windows if this is what I need to
make it work there, too. If so I would also add instructions for
windows to the wiki).
Tomorrow I also want to clean up the buildout in that it uses the
indra packages and we can get rid of svn installs (So that windows
users just need TortoiseSVN but not a commandline svn, which I find
painful as a thought but anyway ;-) ).
Minimum Requirement for Python is 2.4 then which works for me. 2.3
libdev_mac buildout Python 2.5 is required though (should be
sufficient as it's for uptodate macs with Python2.5 anyway).
I also hope a new setuptools release is out soon so we can get rid
of this buildout again as it's also a pain to update 2 buildout.cfg
all the time.
cheers,
Christian
--
http://comlounge.tv
http://mrtopf.de/blog
Luetticher Strasse 10 Skype: HerrTopf
http://comlounge.net
Tel: [phone] E-Mail
Fax: [phone] IRC: MrTopf, Tao_T
neue Show: TOPFt?glich (http://mrtopf.de/blog/category/topf-taglich/)
_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

------------------------------------------------------------------------
_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

[Locklainn]

Enus, I am not added to the JIRA, and can't add myself or add tasks.
Possible to get added?

Tao, the buildout fails on my windows machine when I include eventlet
lines in buildout.cfg. If I remove those lines, along with the
setuptools, it works. I have checked vs2003 and the OpenSSL include and
lib directories are added.

Also, I moved over the test_ogplogin and test_request_rez to testharness
directory. When I run bin\testharness, it doesn't find those tests. What
is going on?

Thanks,
Lock