Vizcayno wrote:
> but the only idea
> that this recommended solution represents a double processing
> (accommodate the list) and double use of memory with 'table' restrained
> me to continue and send this message
'Premature optimization is the root of all evil' :-). In this case, if
only your da
Ivan:
Many thanks for your attention and help. My intention in this occasion
was to gain speed at the moment to show data at the web page. I thought
to do something similar to what you kindly proposed, but the only idea
that this recommended solution represents a double processing
(accommodate the
Vizcayno wrote:
> info_dict = { 'data': lst,
>'poscol': ( 2,0,11,29,18,..)
> return render_to_response('pres_marcaciones.html', info_dict)
Instead of passing this two pieces into template and handle them there
you should do this right in the view and pass already constructed tabl
I have the next big list:
row 1: ['col1','col2','col3', 'col4',..., 'col30']
row 2: ['col1','col2','col3', 'col4',..., 'col30']
row 3: ['col1','col2','col3', 'col4',..., 'col30']
.
.
.
row 4000: ['col1','col2','col3', 'col4',..., 'col30']
the variable name that contains this list is 'lst'
For eac
4 matches
Mail list logo
