Skip to content
This repository has been archived by the owner on Jul 3, 2023. It is now read-only.

Initial release of hamilton #1

Closed
wants to merge 9 commits into from
Closed

Initial release of hamilton #1

wants to merge 9 commits into from

Conversation

skrawcz
Copy link
Collaborator

@skrawcz skrawcz commented May 26, 2020

This creates a package to be released.

I believe I have ported things over correctly.

The pip installable will be sf-hamilton due to naming conflict in pypi.

I have tested this locally with demandpy, and unit tests pass. Once we push a version here, I'll then be able to properly create a branch and have it go through all the tests.

So they're not at the top of the project.
Sorry, lost the commit history here :(
We have to call the package sf-hamilton, since there is already
a hamilton package in pypi.

I moved the version into the hamilton package itself, that way
it's easy to check the running version whereever it ends up being
used.
Add with pre-commit install.
In python 3.6 and python 3.7.
It was writing within hamilton -- that's just unnecessary.
Vestage from old repository. Not required here.
So that things are simpler.
@skrawcz skrawcz changed the title Initial release Initial release on hamilton May 27, 2020
@skrawcz skrawcz changed the title Initial release on hamilton Initial release of hamilton May 27, 2020
@elijahbenizzy
Copy link
Collaborator

Looks good. A thought: we should probably include hamiltime here as well, or in a different repo. Its more closely coupled to the internals of hamilton than demandpy. I think we should do this by including it as a plugin, E.G. an optional feature (installable target) that can be used with hamilton but is not required.

I think we should do this with the initial release, because:
(1) Many code modifications to hamiltime require modifications to hamilton as well
(2) This change clarifies ownership for hamilton/demandpy. We own hamiltime, and should thus have it in our own repo.

Happy to do it as a plugin structure as its really extra functionality on top of hamilton.

@skrawcz skrawcz requested a review from bfollinprm May 27, 2020 16:04
@skrawcz
Copy link
Collaborator Author

skrawcz commented May 27, 2020

@elijahbenizzy sounds good. but 🤔 do we want commit history for hamiltime? If so I'll need to redo everything I think (perhaps I can google it...)

Copy link
Collaborator

@elijahbenizzy elijahbenizzy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@elijahbenizzy sounds good. but 🤔 do we want commit history for hamiltime? If so I'll need to redo everything I think (perhaps I can google it...)

I don't think we need it TBH. In fact, I'd go ahead and say that if we ever open source this we'll want to completely remove commit history, so I'm not too stressed about it. That said, it would be nice to git blame, but most definitely not essential.


from setuptools import setup, find_packages

# don't fail if there are problems with the readme (happens within circleci)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh? Does circleCI just drop the README?

version=VERSION,
description='Hamilton, the micro-framework for creating dataframes.',
long_description=readme,
author='skrawczyk@stitchfix.com, elijah.benizzy@stitchfix.com',
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: looks like author is supposed to be full name whereas the author_email is supposed to be the corresponding emails (in this case the team-email makes sense)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants