[ 
https://issues.apache.org/jira/browse/AIRFLOW-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978376#comment-16978376
 ] 

ASF GitHub Bot commented on AIRFLOW-6019:
-----------------------------------------

eserdyuk-exos commented on pull request #6613: [AIRFLOW-6019] Fix 
KubernetesExecutor Python 3.* dict.iteritems() exception
URL: https://github.com/apache/airflow/pull/6613
 
 
   ### Jira
   https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-6019
   
   ### Description
   `kubernetes_executor.py` didn't support Python 3 cause of `dict.iteritems()` 
using. 
   It has been fixed with the help of `six.iteritems` for a backward 
compatibility.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> KubernetesExecutor iteritems() exception when using Python 3.*
> --------------------------------------------------------------
>
>                 Key: AIRFLOW-6019
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6019
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: executor-kubernetes, executors
>    Affects Versions: 1.10.6
>            Reporter: Eugene Serdyuk
>            Assignee: Eugene Serdyuk
>            Priority: Blocker
>              Labels: kubernetes
>         Attachments: logs.txt
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> When running scheduler using {{KubernetesExecutor}} with Python 3.7 the 
> exception occurs due to the use of {{iteritems()}} within dictionaries.
> {{iteritems()}} found:
> - {{airflow/executors/kubernetes_executor.py}} line 277
> - {{airflow/executors/kubernetes_executor.py}} line 655
>  
> TODO: use {{six.iteritems}} function.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to