Image
EAN-130012236215691   EAN-13 barcode 0012236215691
UPC-A012236215691   UPC-A barcode 012236215691
Product NameWeeds Season 2
LanguageEnglish
CategoryElectronics / Photography: A/V Media: Movie
Amazon.comA Buy on Amazon ~ B000Q6GUKC
Model2287040
Price New2.80 US Dollars    (curriencies)
Price Used1.60 US Dollars    (curriencies)
IMDbIMDb Link
TrailerWatch The Trailer
Run Time28 minutes
Aspect Ratio1.78:1
CastMary-Louise Parker, Hunter Parrish, Alexander Gould, Kevin Nealon
DirectorN/A
GenreCOMEDY,CRIME,DRAMA
Run Time283 minutes
Width5.25 inches    (convert)
Height0.5 inches    (convert)
Length6.75 inches    (convert)
Weight24 hundredths pounds    (convert)
BindingBlu-ray
Release Year20052012
FormatMultiple Formats, AC-3, Blu-ray, Closed-captioned, Color, Dolby, NTSC, Subtitled, Widescreen
Published01/14/2014
Run Time283 minutes
Features
  • Condition: New
  • Format: Blu-ray
  • AC-3; Closed-captioned; Color; Dolby; Subtitled; Widescreen
Long DescriptionAfter her husband's unexpected death and subsequent financial woes, suburban mom Nancy Botwin (Parker) embraces a new profession: the neighborhood pot dealer. As it seems like everyone secretly wants what she's selling -- even city councilman Doug Wilson (Nealon) -- Nancy is faced with keeping her family life in check and her enterprise a secret from her neighbor/pseudo-friend/PTA president, Celia Hodes (Perkins).
Similar Items0683904633569: Who's Harry Crumb? - Retro VHS Style
0191329010143: Molly's Game
0031398240785: Weeds Season 3
0031398213345: Weeds Season 1
0031398164548: Weeds Season 8
0031398145295: Weeds Season 7
0031398127635: Weeds Season 6
0031398114413: Weeds Season 5
0031398109389: Weeds Season 4
0031398108740: Weeds Season 4
Created05-22-2010
Modified05-27-2019 4:59:30am
MD583c0172e8e5c6def9da6bad5b0c4fcfa
SHA256c808409c21e8072cd5dfd6082bb8f24dad44669e00b4259d9c48a92e67a2e596
Search Googleby EAN or by Title
Query Time0.0213740

Article of interest

This describes how to use version 3.x of the data feed. Version 2.x of the feed is still supported. Version 1.x of the feed is no longer supported in any way.

IMPORTANT: Starting with version 3.2, we have a new property and a new way of dealing with product images. Read about it here.

Accessing the data requires your account to have an active data feed. This switch can be turned on or off on the data feed page. This is also where you will be able to view your KEYCODE which is required to make calls to the feed.

Main changes from version 2.x to 3.x include (but not limited to)...

Calls to the data feed are made via HTTP GET or HTTP POST requests. There are only a few required parameters when making a call.

Most other parameters are optional and they will alter the way data is returned to you and how your request is processed. You can also pass in your own values that you need carried through. Any parameter that the system doesn't recognize will be returned AS-IS in the status block. This can be handy in situations where you are pulling the data in an asyncronus manor and need extra information passed into your callback routine.

When performing a lookup...

When updating data...

When deleting data...

There are some special "get" operations that need no other parameters. You would not use "find" or "update" when using these. Only use the "keycode", "mode" and "get" for these items. These operations are important because many of our elements are data driven and that data changes over time. We normally don't remove attributes or categories but we do often add to the collection.

The returned data can come back in JSON or XML format. In either case the structure of the data is the same. Because it is easier to read, we will be using XML to demonstrate the layout of the result. Here is the data layout. Notice that this is a complex object and some elements have child elements and some elements may be arrays with repeating content.

The easiest way to get the feel of the data is to make several requests using your web browser and ask for the data in XML format. Although JSON is often easier to work with in code, the XML output is often easier for people to read because of the nice markup tags that wrap around each element and the web browser will usually do a nice job of indenting to make it clear which elements are stored within other elements.

Close

Search

Close

Share

Close

Dialog