On 21Nov2014 15:57, Clayton Kirkwood wrote:
Got a general problem with url work. I’ve struggled through a lot of
code which uses urllib.[parse,request]* and urllib2. First q: I read
someplace in urllib documentation which makes it sound like either
urllib or urllib2 modules are being deprecated
On Fri, Nov 21, 2014 at 01:37:45PM -0800, Clayton Kirkwood wrote:
> Got a general problem with url work. I've struggled through a lot of code
> which uses urllib.[parse,request]* and urllib2. First q: I read someplace in
> urllib documentation which makes it sound like either urllib or urllib2
> m
>-Original Message-
>From: Joel Goldstick [mailto:joel.goldst...@gmail.com]
>Sent: Friday, November 21, 2014 2:39 PM
>To: Clayton Kirkwood
>Cc: tutor@python.org
>Subject: Re: [Tutor] urllib confusion
>
>On Fri, Nov 21, 2014 at 4:37 PM, Clayton Kirkwood
>wrote:
On 21/11/14 21:37, Clayton Kirkwood wrote:
urllib or urllib2 modules are being deprecated in 3.5. Don’t know if
it’s only part or whole.
urlib2 doesn't exist in Python3 there is only the urllib package.
As to urllib being deprecated, thats the first I've heard of
it but it may be the case - I
On Fri, Nov 21, 2014 at 4:37 PM, Clayton Kirkwood wrote:
> Hi all.
>
>
>
> Got a general problem with url work. I’ve struggled through a lot of code
> which uses urllib.[parse,request]* and urllib2. First q: I read someplace in
> urllib documentation which makes it sound like either urllib or urll
Hi all.
Got a general problem with url work. I've struggled through a lot of code
which uses urllib.[parse,request]* and urllib2. First q: I read someplace in
urllib documentation which makes it sound like either urllib or urllib2
modules are being deprecated in 3.5. Don't know if it's only par
