Re: Make sure you removed all debugging print statements error

2016-08-10 Thread Chris Angelico
On Thu, Aug 11, 2016 at 8:48 AM, Gregory Ewing wrote: > Chris Angelico wrote: >> >> I suppose you could put down Kelvin as a last name and either Baron or >> Lord as a first name, but that'd just be cheating... > > > Or put NULL as the first name and have fun watching > the database break. > > htt

Re: Make sure you removed all debugging print statements error

2016-08-10 Thread Gregory Ewing
Chris Angelico wrote: I suppose you could put down Kelvin as a last name and either Baron or Lord as a first name, but that'd just be cheating... Or put NULL as the first name and have fun watching the database break. http://www.wired.com/2015/11/null/ Or perhaps even profit: http://www.dail

Re: Make sure you removed all debugging print statements error

2016-08-10 Thread Chris Angelico
On Wed, Aug 10, 2016 at 8:21 PM, alister wrote: - but secondly, don't force people's names to be subdivided. >>> >>> I like the French convention >>> . >> >> I may not have a family name at all > > Damn this would have been an id

Re: Make sure you removed all debugging print statements error

2016-08-10 Thread alister
On Wed, 10 Aug 2016 09:23:40 +, alister wrote: > On Tue, 09 Aug 2016 19:53:56 -0700, Lawrence D’Oliveiro wrote: > >> On Tuesday, August 9, 2016 at 4:20:37 AM UTC+12, Chris Angelico wrote: >>> Firstly, the bare "except:" clause should basically never be used; >>> instead, catch a very specific

Re: Make sure you removed all debugging print statements error

2016-08-10 Thread alister
On Tue, 09 Aug 2016 19:53:56 -0700, Lawrence D’Oliveiro wrote: > On Tuesday, August 9, 2016 at 4:20:37 AM UTC+12, Chris Angelico wrote: >> Firstly, the bare "except:" clause should basically never be used; >> instead, catch a very specific exception and figure out what you want >> to do here > >

Re: Make sure you removed all debugging print statements error

2016-08-09 Thread Steven D'Aprano
On Wednesday 10 August 2016 12:53, Lawrence D’Oliveiro wrote: > On Tuesday, August 9, 2016 at 4:20:37 AM UTC+12, Chris Angelico wrote: >> Firstly, the bare "except:" clause should basically never be used; >> instead, catch a very specific exception and figure out what you want to >> do here > > Y

Re: Make sure you removed all debugging print statements error

2016-08-09 Thread Lawrence D’Oliveiro
On Tuesday, August 9, 2016 at 4:20:37 AM UTC+12, Chris Angelico wrote: > Firstly, the bare "except:" clause should basically never be used; > instead, catch a very specific exception and figure out what you want to > do here Yes. > - but secondly, don't force people's names to be subdivided. I l

Re: Make sure you removed all debugging print statements error

2016-08-08 Thread Michael Torrie
On 08/08/2016 06:20 AM, aaryanrevi...@gmail.com wrote: > Hello guys! I was answering a question on a piece of homework of > mine. Sadly I can't answer it correctly due to the repetitive error > being "Make sure you removed all debugging print statements." > Hopefully one of you guys can help me sol

Re: Make sure you removed all debugging print statements error

2016-08-08 Thread Chris Angelico
On Mon, Aug 8, 2016 at 10:20 PM, wrote: > class Person(object): > def __init__(self, name): > self.name = name > try: > firstBlank = name.rindex(' ') > self.lastName = name[firstBlank+1:] > except: > self.lastName = name > se

Re: Make sure you removed all debugging print statements error

2016-08-08 Thread Christian Gollwitzer
Am 08.08.16 um 14:20 schrieb aaryanrevi...@gmail.com:> Hello guys! I was answering a question on a piece of homework of mine. Sadly I can't answer it correctly due to the repetitive error being "Make sure you removed all debugging print statements." Hopefully one of you guys can help me solve th

Re: Make sure you removed all debugging print statements error

2016-08-08 Thread Steven D'Aprano
On Mon, 8 Aug 2016 10:20 pm, aaryanrevi...@gmail.com wrote: > Hello guys! I was answering a question on a piece of homework of mine. > Sadly I can't answer it correctly due to the repetitive error being "Make > sure you removed all debugging print statements." Hopefully one of you > guys can help