python 3.x - Contradicting Errors? -


so i'm trying edit csv file writing temporary file , replacing original temp file. i'm going have edit csv file multiple times need able reference it. i've never used namedtemporaryfile command before , i'm running lot of difficulties. persistent problem i'm having writing on edited lines.

this part goes through , writes on rows unless specific values in specific column , passes over.

i have this:

office = 3 temp = tempfile.namedtemporaryfile(delete=false)  open(infile, "rb") oi, temp:     r = csv.reader(oi)     w = csv.writer(temp)      row in r:         if row[office] == "r00" or row[office] == "alc" or row[office] == "rms":             pass         else:             w.writerow(row)

and error:

traceback (most recent call last): file "h:\jcatoe\practice python\pract.py", line 86, in <module>   cleanofficecol() file "h:\jcatoe\practice python\pract.py", line 63, in cleanofficecol   row in r: _csv.error: iterator should return strings, not bytes (did open file in text mode?)

so searched error , general consensus "rb" needs "rt" tried , got error:

traceback (most recent call last): file "h:\jcatoe\practice python\pract.py", line 86, in <module>   cleanofficecol() file "h:\jcatoe\practice python\pract.py", line 67, in cleanofficecol   w.writerow(row) file "c:\users\jcatoe\appdata\local\programs\python\python35-32\lib\tempfile.py", line 483, in func_wrapper   return func(*args, **kwargs) typeerror: bytes-like object required, not 'str'

i'm confused because errors seem saying opposite thing.

if read tempfile docs you'll see default it's opening file in 'w+b' mode. if take closer @ errors, you'll see you're getting 1 on read, , 1 on write. need doing making sure you're opening input , output file in same mode.

you can this:

import csv import tempfile  office = 3 temp = tempfile.namedtemporaryfile(delete=false)  open(infile, 'r') oi, tempfile.namedtemporaryfile(delete=false, mode='w') temp:     reader = csv.reader(oi)     writer = csv.writer(temp)      row in reader:         if row[office] == "r00" or row[office] == "alc" or row[office] == "rms":             pass         else:             writer.writerow(row)

Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more