-
Notifications
You must be signed in to change notification settings - Fork 704
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
Release 2.2.1 #321
Comments
I plan to work on release on Sunday |
@filmor I don't see a tag for |
I deleted the 2.2.0 tag before, because I found some issues. For me the
release blocking is the issue with embedding CPython on Linux. Right now
either extending or embedding works on Linux, but not both at the same time.
…On Mon, Jan 9, 2017, 11:58 AM Victor Uriarte ***@***.***> wrote:
@filmor <https://github.com/filmor> I don't see a tag for v2.2.0. The
draft references the tag, but doesn't actually point to an existing one.
Not sure if someone already deleted it but marking that first item out :)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#321 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5faALB42SKOs4xJyW11TiWFEFiQyks5rQnVGgaJpZM4LeZqI>
.
|
I'm not familiar with the issue since I work on windows. @denfromufa was that an issue introduced on or after |
release cut for Anaconda looks like tomorrow |
@stonebig I'm able to access pythonnet on anaconda now. I plan to work on release tonight. |
tonight ? |
I'm working on it
…On Sat, Jan 21, 2017, 1:42 PM stonebig ***@***.***> wrote:
tonight ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#321 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5Ta-r_vcSo5odhbKnoUvFI6A3HNDks5rUl-1gaJpZM4LeZqI>
.
|
@filmor @vmuriart I removed this from v2.2.0 based on our discussion:
But I also added this:
|
good call on testpypi. Though I think @tonyroberts only gave you access to the pypi account. |
@vmuriart I have access to both pypi from @tonyroberts and to testpypi from @davidanthoff |
@denfromufa yes on both pypi and testpypi. |
tonight ? |
Couldn't resist... |
completed the changes, but the prior I'll bump everything to |
ehh on second though, I'd rather bump the version to Thoughts? @filmor @denfromufa |
Let's not rewrite the history, bumping third digit is fine. We can make
v2.2.0 with some commits between last release and now, if you can justify
v2.3.0 release.
Also if you would like to release to pypi yourself, please do it to
testpypi first for 1-2 day testing.
…On Thu, Jan 26, 2017, 11:41 PM Victor Uriarte ***@***.***> wrote:
ehh on second though, I'd rather bump the version to 2.3.0 and treat
2.2.0-dev1 as the 2.2.0 release.
Thoughts? @filmor <https://github.com/filmor> @denfromufa
<https://github.com/denfromufa>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#321 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5fxWaX9hjHCylJD2nxpZNnHERMaGks5rWYObgaJpZM4LeZqI>
.
|
Actually if we make The test package is in |
No source distribution for Linux?
…On Fri, Jan 27, 2017, 12:16 AM Victor Uriarte ***@***.***> wrote:
Actually if we make v2.2.0 a commit between last release and now, then we
would be rewriting history 😄
v2.2.1 is fine, it just didn't sound right when I wrote it in the
CHANGELOG.
The test package is in testpypi.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#321 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5XfoeAAYZZgCATI8n1EO-_HWDnSqks5rWYvBgaJpZM4LeZqI>
.
|
I had a small mess up on the initial release to |
It is OK if we bump to 2.2.1. I had the same issue with clrmagic. Also
please use twine to upload stuff, unless there is something better.
Let me get to anaconda.org repo tomorrow.
…On Fri, Jan 27, 2017, 12:22 AM Victor Uriarte ***@***.***> wrote:
I had a small mess up on the initial release to testpypi ... 😢. Since it
won't let you re-upload the package its locked.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#321 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5RCqQbW3_jEoAxtAZC7FTJPCdKVYks5rWY01gaJpZM4LeZqI>
.
|
If we bump tag, then setup.py, `__version__`, release notes and elsewhere
need to be updated to v2.2.1 as well.
On Fri, Jan 27, 2017, 12:34 AM Denis Akhiyarov <denis.akhiyarov@gmail.com>
wrote:
… It is OK if we bump to 2.2.1. I had the same issue with clrmagic. Also
please use twine to upload stuff, unless there is something better.
Let me get to anaconda.org repo tomorrow.
On Fri, Jan 27, 2017, 12:22 AM Victor Uriarte ***@***.***>
wrote:
I had a small mess up on the initial release to testpypi ... 😢. Since it
won't let you re-upload the package its locked.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#321 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5RCqQbW3_jEoAxtAZC7FTJPCdKVYks5rWY01gaJpZM4LeZqI>
.
|
Everyone, FYI here is release to testpypi for testing: https://testpypi.python.org/pypi/pythonnet/2.2.0 The tags on top are missing py3.6, still shows 2.2.0.dev1 |
The tags get updated when its uploaded to |
@vmuriart for some reason (ana)conda package is still 2.2.0-dev1, let me try to resolve: |
@vmuriart the conda package is looking at git tags, which I also updated: https://github.com/pythonnet/pythonnet/releases/tag/v2.2.1 But this will now rebuild all packages, so may need to re-upload to testpypi (I guess except source distribution). |
On Fri, Jan 27, 2017 at 22:41 denfromufa ***@***.***> wrote:
@vmuriart <https://github.com/vmuriart> the conda package is looking at
git tags, which I also updated:
https://github.com/pythonnet/pythonnet/releases/tag/v2.2.1
But this will now rebuild all packages, so may need to re-upload to
testpypi (I guess except source build).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#321 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMr87L2xoh0Zuqx7FnuCmwAFrXnfH-Ecks5rWtUCgaJpZM4LeZqI>
.
The source itself didn't change. It should be fine. Sadly can't reupload to
test pypi though without rebumping version
|
@vmuriart @jreback please try out conda package from anaconda.org:
https://anaconda.org/pythonnet/pythonnet I could add @vmuriart to package managers, but not @filmor and @tonyroberts because they are already registered. |
@stonebig do you have a chance to test out pythonnet from testpypi in winpython? pip install -i https://testpypi.python.org/pypi pythonnet -U --force |
nice checklist for the future versions: |
@denfromufa pythonnet-2.2.0 is already shipped and uploaded.... re-doing a rc3.... bump winpython package version to cleanup my own numbering mess |
@stonebig we bumped the version number to v2.2.1 |
@denfromufa ok to finalize release to pypi? |
Sure! Let's do it and then send the reddit and hacker news posts ;)
…On Sat, Jan 28, 2017, 8:19 AM Victor Uriarte ***@***.***> wrote:
@denfromufa <https://github.com/denfromufa> ok to finalize release to
pypi?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#321 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5aib7T-PKpiY1l5uG8AiU1IYysgAks5rW05_gaJpZM4LeZqI>
.
|
done |
@denfromufa can you grant me repository creation rights on the github account? I want to create the dummy repository to check release under Pythonnet account but didn't have write access. |
@vmuriart done! |
@denfromufa Thanks! one last thing... I tried checking my access on the Anaconda package. I got the email asking to confirm access to the package, but didn't grant me rights to it. |
@vmuriart i sent a support request to Continuum folks, but their support is very limited for free accounts. |
I guess it's general consensus (even though we have a
v2.2.0
tag which is incompatible with our conda recipe) that we haven't released, yet, so I'd like to list up what's to do and to merge before we deem this done (and maybe we'll hold off merging new features until then):v2.2.0
tagFix issue MSTests failing when importing a module with imports #262 ?2.2.1
The text was updated successfully, but these errors were encountered: