[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2018-09-13 Thread Scott Jungwirth (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614227#comment-16614227 ] Scott Jungwirth commented on BEAM-3106: --- It looks like this particular issue (bigquery) will be

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2018-09-13 Thread Robert Bradshaw (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614093#comment-16614093 ] Robert Bradshaw commented on BEAM-3106: --- Our main requirements now specify version ranges (generally

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2018-09-13 Thread Scott Jungwirth (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614047#comment-16614047 ] Scott Jungwirth commented on BEAM-3106: --- I just ran into this issue using Google's Cloud Composer

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2018-08-08 Thread Ahmet Altay (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574053#comment-16574053 ] Ahmet Altay commented on BEAM-3106: --- [~cclauss] I am not familiar with pipenv. Could you explain how it

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2018-08-08 Thread cclauss (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16572766#comment-16572766 ] cclauss commented on BEAM-3106: --- What about moving to https://docs.pipenv.org ? > Consider not pinning all

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2018-01-26 Thread Ahmet Altay (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341914#comment-16341914 ] Ahmet Altay commented on BEAM-3106: --- I mentioned upgrading the libraries that beam depends on the their

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2018-01-26 Thread RK (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16341912#comment-16341912 ] RK commented on BEAM-3106: -- This can result in some difficult-to-pin-down errors in the google-cloud-platform

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2018-01-05 Thread Ahmet Altay (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313731#comment-16313731 ] Ahmet Altay commented on BEAM-3106: --- [~m...@maxroos.com] if it helps you can upgrade Beam's bigquery

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2018-01-05 Thread Maximilian Roos (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313574#comment-16313574 ] Maximilian Roos commented on BEAM-3106: --- Thanks for your earlier responses Ahmet. To give a

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2017-10-28 Thread Ahmet Altay (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223793#comment-16223793 ] Ahmet Altay commented on BEAM-3106: --- This plan sounds good to me. Thank you. I will unassign so that

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2017-10-28 Thread Maximilian Roos (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223716#comment-16223716 ] Maximilian Roos commented on BEAM-3106: --- > What do you think about a policy like, reviewing capped

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2017-10-27 Thread Ahmet Altay (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16222761#comment-16222761 ] Ahmet Altay commented on BEAM-3106: --- The advantage of putting them in {{setup.py}} is that the package

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2017-10-27 Thread Maximilian Roos (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16222698#comment-16222698 ] Maximilian Roos commented on BEAM-3106: --- Yes, those are good points, and this is a tough problem;

[jira] [Commented] (BEAM-3106) Consider not pinning all python dependencies, or moving them to requirements.txt

2017-10-27 Thread Ahmet Altay (JIRA)
[ https://issues.apache.org/jira/browse/BEAM-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16222645#comment-16222645 ] Ahmet Altay commented on BEAM-3106: --- The reason behind pinning or capping dependencies is to prevent