Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source DuckDB: ✨ Add MotherDuck support 🦆🦆 #29428
Source DuckDB: ✨ Add MotherDuck support 🦆🦆 #29428
Changes from 42 commits
80306e2
a331b01
cb63810
a0b4a2a
74c68eb
29f3704
ec275a5
8a67d3c
622e34d
e708c08
58b4ab8
b48432e
60a1166
401cd3b
be903ae
6907b06
6c69415
a4659b7
8f62a79
0fdbe90
9cb65d9
742364d
ef0e648
967b8e2
d5dd6d0
7970318
0a6cfaa
aa1d258
646ccdf
07294d9
735d3a6
6d09f3d
a315a3e
a994139
1e7e998
db58015
03f6efb
5c15c51
32b6c34
52f31e6
56d4186
044fbe8
a585701
d65c853
07c2e5c
23b21ca
65161fd
41a9981
2b31870
f290c2b
92897fd
811d601
611b915
e0ec605
1e7b3b7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alafanechere Having to install poetry at this level has left me with a thought for when we start removing dockerfiles from python connectors.
The thought is that we have to be really clear in our code and file structure that there is an order of operations.
In step 1 we will have to detect
In step 2 we will have to
In step 3 we will have to
And we will likely need to have step 3 generic enough to be used to
With all that in mind I think we should start spliting environments.py into a structure based around these different types of interchangable systems like this
Anyway no action required. Just wanted to raise the thought, in case you objected to me moving in this direction
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bnchrch we're aligned.
Just a detail about step 3:
The main change I plan to make is:
python
base image on top of which we install stuffs like poetry, pytest etc. I don't like this approach because it means tests are executed in a different environment from which the actual connector code is executed in the wild (its docker container)pip install .[test]
forsetup.py
orpoetry install --with test
. This will ensure consistency: tests will be run in the same execution context as the actual "prod" environment.We should indeed implement a switch like statement to run different command according to the detected package manager in use. (edit: I just saw that you implemented this below)
I'm happy to revisit the
environments
packages (we can also reconsider its legitimacy). I originally named itenvironements
to collect reusable containers with pre-installed tools. My target suggestion will discard the provisionning of atest
environment.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bnchrch I think we should add
poetry
to our base python image. Wdyt? I can add it in #30303This file was deleted.