The DateField example runs correctly in pyjd, even with my time zone, so
the bug is specific to the compilation over to javascript. Unfortunately,
at this point, I have to surrender because my knowledge of Javascript (as
well as the pyjamas compiler) is zero, and, sadly, I won't have the time
necessary to get my head around it right now.

Thank you all for so much help. I took a crack at this problem as best I
could.

David

On Tue, Apr 3, 2012 at 09:00, David Ripplinger <[email protected]> wrote:

> I sincerely apologize for not reading the README.txt in greater detail. I
> had read the INSTALL.txt and (shame on me) assumed that it contained all
> the info I needed to get pyjd installed.
>
> David
>
>
> On Tue, Apr 3, 2012 at 04:26, lkcl luke <[email protected]> wrote:
>
>> On Tue, Apr 3, 2012 at 9:03 AM, Peter Bittner <[email protected]>
>> wrote:
>> > 2012/4/3 lkcl luke <[email protected]>:
>> >>  read the INSTALL.txt, the standard file which is to be read prior to
>> >> installation of any application, which has been the standard location
>> >> for nearly three decades of computer science.
>> >
>> > I thought that was README.txt...?   ("... three decades of ...")
>> >
>> > ;-)
>>
>>  rhhmmm... i should be banned from using a computer at 8:30am, 5
>> minutes after getting up.  severely dehydrated.  mrrrm....
>>
>>  but seriously, david (and others who may have joined the list
>> recently): your first automatic reaction on downloading any python
>> package should be to look for a README and/or an INSTALL file and
>> actually read them both *before* proceeding.
>>
>>  there do exist some things like automatic package installation
>> systems - ezzhhhh setup for example, or zope's buildout system - we do
>> *not* use those because they tend to screw up (bypass and disrespect)
>> standard gnu/linux distribution packaging systems.  plus they're a
>> hell of a lot of extra crap.
>>
>>  so that means that, on e.g. w32 systems you need to download the
>> dependencies manually (of which there is one - python-comtypes).
>>
>>  l.
>>
>
>

Reply via email to