packer gridded widgets can optionally be made sticky on one side of their allocated cell space (such as anchoror on more than one side to make them stretch (such as fillwidgets can be made sticky in four directions--nseand wand concatenations of these letters specify multiple-side stickiness for instancea sticky setting of left justifies the widget in its allocated space (such as packer anchor= )and ns stretches the widget vertically within its allocated space (such as packer fill=ywidget stickiness hasn' been useful in examples thus far because the layouts were regularly sized (widgets were no smaller than their allocated grid cell space)and resizes weren' supported at all herethoughexample - specifies nsew stickiness to make widgets stretch in all directions with their allocated cells different combinations of row and column weights and sticky settings generate different resize effects for instancedeleting the columnconfig lines in the grid script makes the display expand vertically but not horizontally try changing some of these settings yourself to see the sorts of effects they produce spanning columns and rows there is one other big difference in how the grid script configures its windows both the grid and the pack windows display label on the top that spans the entire window for the packer schemewe simply make label attached to the top of the window at large (rememberside defaults to top)label(roottext='pack'pack(because this label is attached to the window' top before any row frames areit appears across the entire window top as expected but laying out such label takes bit more work in the rigid world of gridsthe first line of the grid implementation function does it like thislabel(roottext='grid'grid(columnspan= to make widget span across multiple columnswe pass grid columnspan option with spanned-column count hereit just specifies that the label at the top of the window should stretch over the entire window--across both the label and the entry columns to make widget span across multiple rowspass rowspan option instead the regular layouts of grids can be either an asset or liabilitydepending on how regular your user interface will bethese two span settings let you specify exceptions to the rule when needed so which geometry manager comes out on top herewhen resizing is factored inas in the script in example - gridding actually becomes slightly more complexin factgridding requires three extra lines of code on the other handenumerate could again make the race closegrid is still convenient for simple formsand your grids and packs may vary grids