Re: [Tutor] slashes in paths

2013-07-20 Thread Dave Angel
On 07/20/2013 08:24 PM, Steve Willoughby wrote: On 20-Jul-2013, at 16:37, Jim Mooney wrote: If only Bill Gates hadn't chosen '\', which is awkward to type and hard to make compatible - but I think he figured his wonderful DOS would be a Unix-killer, reign supreme, and there would be no compati

Re: [Tutor] slashes in paths

2013-07-20 Thread Dominik George
Hi, the base path is \, and one exists for every drive. C:\foo is foo in C:'s root, C:foo is foo in C:'s current working directory. -nik Jim Mooney schrieb: >On 20 July 2013 13:46, Alan Gauld wrote: > >> The fact that you gave it a prefix containing forward >> slashes is confusing things.

Re: [Tutor] slashes in paths

2013-07-20 Thread Dominik George
Hi Jim, > But oddly, it makes all slashes forward if I end the path with a > forward slash, so it's not consistent with itself. It is, in the sense that it preserves any form of seperator that is already there. It just doesn't throw away what you want to be there: >>> import ntpath >>> ntpath.

Re: [Tutor] slashes in paths

2013-07-20 Thread Alan Gauld
On 20/07/13 19:24, Jim Mooney wrote: I was looking at os.path.join, which is supposed to join paths intelligently. It does including taking account of OS specific separators. Which in the case of Windows is notionally the backslash. The fact that you gave it a prefix containing forward slashes

Re: [Tutor] 3 Dimensional Dictionaries

2013-07-20 Thread Alan Gauld
On 20/07/13 11:17, Sunil Tech wrote: Hi Everyone, I have a list of dictionaries like world = [{'continent':'Asia','continent_code':1,'ocean':'Pacific','country':'India','country_code':1,'state':'Kerala', 'state_pin':51}, i am trying to to make it in this format

Re: [Tutor] slashes in paths

2013-07-20 Thread Dominik George
Hi, > >>> soundfile13 > 'c:/python27/jimprogs/wav\\bicycle_bell.wav' > >>> > > with single forward slashes mixed with a double backslash > > it comes out even worse if I print it > > c:/python27/jimprogs/wav\bicycle_bell.wav - no double backslash, > which could create a mess if someone copied

Re: [Tutor] 3 Dimensional Dictionaries

2013-07-20 Thread Steven D'Aprano
On 20/07/13 20:17, Sunil Tech wrote: Hi Everyone, I have a list of dictionaries like Hi Sunil, A couple of style issues here. Please put spaces between parts of your code, for two reasons. Firstly, it makes it a lot easier to read, or perhaps I should say, notusingspacesmakesitmuchharder

Re: [Tutor] 3 Dimensional Dictionaries

2013-07-20 Thread Dave Angel
On 07/20/2013 06:17 AM, Sunil Tech wrote: Hi Everyone, I have a list of dictionaries like world = [{'continent':'Asia','continent_code':1,'ocean':'Pacific','country':'India','country_code':1,'state':'Kerala', 'state_pin':51}, {'continent':'Asia','continent_code':1,'ocean':'Pacific','coun

Re: [Tutor] 3 Dimensional Dictionaries

2013-07-20 Thread Sunil Tech
Hi, yes Dominik & the result should be in that format as stated. On Sat, Jul 20, 2013 at 3:58 PM, Dominik George wrote: > Hi, > > > world = > > > [{'continent':'Asia','continent_code':1,'ocean':'Pacific','country':'India','country_code':1,'state':'Kerala', > > 'state_pin':51}, > > [...] >

Re: [Tutor] 3 Dimensional Dictionaries

2013-07-20 Thread Dominik George
Hi, > world = > [{'continent':'Asia','continent_code':1,'ocean':'Pacific','country':'India','country_code':1,'state':'Kerala', > 'state_pin':51}, > [...] > > i am trying to to make it in this format > to clarify the task at hand: this is comparible to SQL's GROUP BY clause, right? -nik -

[Tutor] 3 Dimensional Dictionaries

2013-07-20 Thread Sunil Tech
Hi Everyone, I have a list of dictionaries like world = [{'continent':'Asia','continent_code':1,'ocean':'Pacific','country':'India','country_code':1,'state':'Kerala', 'state_pin':51}, {'continent':'Asia','continent_code':1,'ocean':'Pacific','country':'India','country_code':1,'state':'Karnat

Re: [Tutor] suggestions for splitting file based on date

2013-07-20 Thread Dave Angel
On 07/20/2013 01:00 AM, Sivaram Neelakantan wrote: On Sat, Jul 20 2013,Dave Angel wrote: These are small,fixed line extracts. Once you determine the offset in the file for those 180, 90, and 30 day points, it's a simple matter to just seek to one such spot and process all the records