[Grok-dev] Neanderthal news

Aroldo Souza-Leite asouzaleite at gmx.de
Thu Aug 2 07:09:04 EDT 2007


here is an update of the Neanderthal Grok sprint announcement.





First week of October 2007
(Monday 1st to Friday 5th)


GfU Cyrus AG in Cologne-Deutz, 10 minutes away from the Cologne main 
railway station.

Who should participate:

Grok developers (this mailinglist) or Python programmers with 
programming experience enough to contribute to Grok.

Already confimed participation:

Martijn Faassen (guest of honour)
Luciano Ramalho
Uli Fouquet
Lennart Regebro

Aroldo Souza-Leite <asouzaleite at gmx.de>
Philip Clooth <pclooth at gfu.net>

Working, eating and sleeping at Neanderthal:

The sprinters will be treated as GfU regular seminar participants. A 
regular a regular seminar room and all other facilities of the seminar 
centre can be used by the sprinters. The Neanderthal sprinters, like the 
participants of other GfU seminars, have lunch in the GfU buffet canteen 
for free.

Cologne is a trade fair city, so that hotels are in general expensive 
and reservations difficult to manage. The GfU has a long experience with 
hotel reservations for seminar participants. For sprinters that reserve 
their rooms in a GfU contract hotel early enough, the GfU is willing to 
subsidise the sprinter's stay so that it will not cost him more than 40 
Euros a night. In the alternative case, if the sprinter prefers to rent 
a room in another hotel and pay the full price, the GfU will provide 
organisational help to find one.

The sprint organisers will take care of the trasport from the city 
centre to the sprint venue.

Cultural events:

On Wednesday (October 3rd) we are working only half day and going to 
Neanderthal in the early afternoon.

Apart from the most original Caveman in person, there is a lot more to 
see in the Rheinland area.

About the sprint organisers:

The DZUG Rheinland (also rzug) is a regional group of members and 
supporters of DZUG e.V. (http://www.dzug.org), the German Speaking Zope 
User Group. The Rheinland is the area around the middle part of the 
Rhine, where Bonn, Cologne, Du"sseldorf and Aachen (Aix-la-Chapelle) are 
the main cities.

About the sprint host:

The GfU Cyrus AG is a traditional corporate IT training and consulting 
company. It organises learning groups from insurance companies, banks 
and state agencies. The GfU sends lecturers to other cities to give the 
groups inhouse courses or brings the groups to Cologne to reside for 3 
to 5 days in the GfU contract hotels and attend courses at the GfU 
seminar centre in Deutz.

The GfU spectrum includes all possible programming languages and 
branches of free and proprietary information technology. However, the 
company directors have been showing a special interest in technologies 
involving OpenSource software. They are planning to expand their Python 
marketing considerably.

There is no "to-do" list from the GfU for the Neanderthal sprint. The 
sprint aims should be discussed in this mailinglist and should fit the 
general Grok roadmap in the first place. The GfU only hopes that Grok 
leads seamlessly to Zope proper it its technical and didactic aspect. A 
welcome by-product of the Grok development would be good documentation, 
tutorials and structured sets of examples like Philipp von 
Weitershausen's worldcookery. This would help in case the GfU decides to 
use Grok as an introductory learning tool in seminars of Zope Component 
Architecture for Python programmers.


grok-dev-request at zope.org schrieb:
> Send Grok-dev mailing list submissions to
> 	grok-dev at zope.org
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mail.zope.org/mailman/listinfo/grok-dev
> or, via email, send a message with subject or body 'help' to
> 	grok-dev-request at zope.org
> You can reach the person managing the list at
> 	grok-dev-owner at zope.org
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Grok-dev digest..."
> Today's Topics:
>    1. Re: Testing a container which uses a custom NameChooser
>       (Darryl Cousins)
> ----------------------------------------------------------------------
> Message: 1
> Date: Wed, 01 Aug 2007 14:04:22 +1200
> From: Darryl Cousins <darryl at darrylcousins.net.nz>
> Subject: Re: [Grok-dev] Testing a container which uses a custom
> 	NameChooser
> To: Luciano Ramalho <luciano at ramalho.org>
> Cc: Grok-dev list <grok-dev at zope.org>
> Message-ID: <1185933862.4972.11.camel at localhost.localdomain>
> Content-Type: text/plain
> Hi Luciano,
> On Tue, 2007-07-31 at 08:57 -0300, Luciano Ramalho wrote:
>> On 7/31/07, Darryl Cousins <darryl at darrylcousins.net.nz> wrote:
>>> import grok
>>> grok.grok('kirbi')
>> Thanks a lot, Darryl!
>> I saw those calls in the grok tests themselves, but I wasn't sure they
>> were needed when testing grok apps (as opposed to testing grok
>> itself).
>> I'll contribute a testing mini-tutorial...
>> Now I have two further questions concerning the same test (further along):
>> 1) Should I convert *all* strings into unicode for use with Zope 3 or
>> does it still use or prefer plain strings for some purposes? I noticed
>> the __name__ of the contained objects was converted by Zope to
>> unicode.
> If you mean strings that are used as attributes such as TextLine or Text
> then you will need to use unicode.
>> 2) In the pac.py module [1] there is a subscriber declared like this:
>> @grok.subscribe(Book, grok.IObjectAddedEvent)
>> def bookAdded(book, event):
>>     if not book.title:
>>         pac = book.__parent__
>>         pac.pending_isbns.append(book.isbn13)
>> [1] http://svn.zope.org/Sandbox/luciano/kirbi/src/kirbi/pac.py?rev=78499&view=markup
>> (or http://tinyurl.com/3ybsed)
>> The last line of the doctest reproduced below aims to test that event,
>> but it's failing. However, when I try the live app, it works. Do I
>> need some additional registration to make the test pass?
> Yes, event testing needs to be setup. Check grok/tests/test_grok.py.
> You could use test_grok set up directly in your tests:
> >from grok.test import test_grok
> def test_suite():
>     modules = ['app', 'pac', 'book']
>     suite = unittest.TestSuite()
>     for module in modules:
>         module_name = 'kirbi.' + module
>         test = doctest.DocTestSuite(module_name,
>                         setUp=test_grok.setUpZope,
>                         tearDown=test_grok.cleanUpZope)
>         suite.addTest(test)
>     return suite
> test_grok.setUpZope set ups event testing for you.
> Eventually you will likely need to write your own setUp method to ensure
> registrations that your application uses. Check zope.app.testing for
> more examples.
> Hope this helps,
> Darryl
>> Regards,,
>> Luciano
>> <TEST>
>> ==============================================
>> Pac: The Public Access Catalog container class
>> ==============================================
>> A Pac is designed to store book records. Let's create one and put a few
>> books in it::
>>   >>> import grok
>>   >>> grok.grok('kirbi')
>>   >>> from kirbi.pac import Pac
>>   >>> from kirbi.book import Book
>>   >>> pac = Pac()
>>   >>> pac.addBook(Book(u'Zero'))
>>   'k0001'
>>   >>> pac.addBook(Book(isbn13='978-0670030583'))
>>   '9780670030583'
>>   >>> pac.addBook(Book(u'A Tale of Two Cities', isbn13='978-0141439600'))
>>   '9780141439600'
>>   >>> sorted(pac)
>>   [u'9780141439600', u'9780670030583', u'k0001']
>> One of the books has ISBN but no Title, so it's put in the fetch queue::
>>   >>> pac.pending_isbns
>>   ['9780670030583']
>> </TEST>
> ------------------------------
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
> End of Grok-dev Digest, Vol 11, Issue 1
> ***************************************

More information about the Grok-dev mailing list