html tags and python

Hansan none
Mon Mar 28 18:25:33 CEST 2005

I figured it out with a lot of if else statements, but still if one have 
time to explain how the time/date modul works with forms, I will be more 
than happy to lear.


"Hansan" <none> wrote in message 
news:4247bc82$0$22679$ba624c82 at
> Hi and thanks for your replies.
> Will one still tell me how I use the timedate modul with my form
> print '''<form action=''><br>
>        <p>Day (1-31):<br> <INPUT type="text" NAME="day">
>        <p>Month (1-12):<br> <INPUT type="text" NAME="month">
> print '''<p><input type=submit value='Submit'></p></form>'''
> ------------------------------------------------------------------------------------------
> It is starting to make a little sense. But its still not that clear...
> If I import the DateTime or install and import the mx package.
> Where should I then change something in my code?
> I guess that I will have to see if the entered number is valid when the 
> user
> clicks the submit button.
> So it must be when I run my script.
> So will I have to import the DateTime modul in my form.script or in my
> insertevent.script
> And this maybe sound stupid, but will one pls give me an example of what 
> the
> code could be for maybe January and February.
> I just cant figure out how they work together, the DateTime modul and the
> html form.
> The user can enter a number in the month field and in the day field. Then
> there have to be a tjeck to see if the entered numbers are valid. If the
> number entered in the month field is 1 and the number entered in the day
> field is 32, there have to come anerror report, and the user will get a
> second try to enter the right numbers.
> And then if the entered numbers are correct, the data will be inserted in
> the database ( But I will work on this if condition myself, I think I can
> figure that out:)
> "Jeremy Bowers" <jerf at> wrote in message 
> news:pan.2005. at
>> On Sat, 26 Mar 2005 18:07:01 -0800, EP wrote:
>>> Then... about the time you start to try to build a real application with
>>> JavaScript, it will start to drive you mad... and you will have a new,
>>> greater affection for Python.
>> Actually, if you dig into it really hard, it's not bad. In fact of all 
>> the
>> languages I know, Javascript is probably the closest to Python circa 
>> 1.5.2
>> that I can think of. Not identical, and it doesn't have *any* of the 
>> later
>> nice things in Python (metaclasses, descriptors, list comprehensions,
>> etc.), the OO can be clumsy (though it is fairly functional), and there
>> are inconveniences that I really wish I could make go away, but it's not
>> too bad.
>> (The worst being that
>> for (var something in someArray) {}
>> gives you the *indices* of the array, not the values, so the next line is
>> almost always
>>  var theActualStinkingValue = someArray[something];
>> .)
>> The DOM is clumsy, but for any given browser not to bad. The 
>> *differences*
>> in the DOMs from browser to browser are what kill you. And of course, no
>> real "libraries".

More information about the Python-list mailing list