Menu
▾
▴
python-control-developers
|
From: Richard M. <mu...@cd...> - 2014-11-26 01:45:26
|
That's definitely confusing. There are two things going on: * We switched the version numbering scheme from 0.6x to 0.6.m * We are not being clear about released versions versus development versions Here's what I think the state of everything is: * Version 0.6d (= 0.6.4) is the latest stable release. That always leaves on sourceforge. * Version 0.6.5 is the current development version, which lives on github. It is not yet release and may not be stable. * I have no clue where version 0.6.6 came from that is on PyPI. James? Clancy? Scott? I'm cc'ing the developers list so that we can fix this. I'll also generate an issue on github so we can track this. -richard > On 25 Nov 2014, at 2:57 , Emmanuel Sérié <es...@gm...> wrote: > > Hi Mr Richard Murray, > > I'm trying to get your package python-control but I am a little bit confused with the different versions available on different sites. > > On pypi, there is a version 0.6.6: > https://pypi.python.org/pypi/control/0.6.6 > > in Github, the master is in version 0.6.5 > > in Sourceforge, the package is in version 0.6d > > which version is the correct one? > > Thanks, > > Emmanuel Sérié. > > > > > 2014-08-10 0:37 GMT+02:00 Richard Murray <mu...@cd...>: > Following a discussion on the developers list, the source code repository and issues tracking for python-control package have been shifted from SourceForge to GitHub. User support for python-control remains on SourceForge, including downloads of the latest release, code documentation, and user discussion lists. > > If you are a user of python-control, you can continue to use SourceForge as the primary location of file downloads and user documentation: > > http://python-control.sourceforge.net/ > http://python-control.sourceforge.net/manual/ > > The current release of python-control is 0.6d, release on 22 March 2014. A new version should be coming sometime this summer. > > In addition to shifting the development environment to GitHub, we have change the python-control-discuss mailing list from a developers-only list to a general discussion list. Feel free to use that list if you want to see discussions about usage of the package: > > https://lists.sourceforge.net/lists/listinfo/python-control-discuss > > This list (python-control-announce) will continue to be a low-volume mailing list with posts regarding new releases of the package or other major updates. > > For those who are interested in the very latest version of python-control, you can clone the python-control project on github: > > https://github.com/python-control/python-control > > -richard > > > ------------------------------------------------------------------------------ > _______________________________________________ > python-control-announce mailing list > pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-control-announce > |
|
From: Scott C. L. <sli...@cd...> - 2014-11-26 18:35:35
|
I suspect there was an (accidental?) upload by jgoppert because the fork under @jgoppert has a setup.py with a micro version of 6, and the commit on that fork that introduced it, https://github.com/jgoppert/python-control/commit/38d5c95fd4de6251fc83179fdfc2245874ebcb7e has a date of one day before the date of the release on PyPI. Two more sources of clues are * issue #37, https://github.com/python-control/python-control/issues/37 * pull request #38, https://github.com/python-control/python-control/pull/38 |
|
From: Emmanuel S. <es...@gm...> - 2014-11-26 21:30:45
|
Tanks for the clarification. I also noticed that an authentification is needed on github to be able to do a git clone, is it normal? Emmanuel Sérié > Le 26 nov. 2014 à 02:45, Richard Murray <mu...@cd...> a écrit : > > That's definitely confusing. There are two things going on: > > * We switched the version numbering scheme from 0.6x to 0.6.m > * We are not being clear about released versions versus development versions > > Here's what I think the state of everything is: > > * Version 0.6d (= 0.6.4) is the latest stable release. That always leaves on sourceforge. > * Version 0.6.5 is the current development version, which lives on github. It is not yet release and may not be stable. > > * I have no clue where version 0.6.6 came from that is on PyPI. James? Clancy? Scott? > > I'm cc'ing the developers list so that we can fix this. I'll also generate an issue on github so we can track this. > > -richard > >> On 25 Nov 2014, at 2:57 , Emmanuel Sérié <es...@gm...> wrote: >> >> Hi Mr Richard Murray, >> >> I'm trying to get your package python-control but I am a little bit confused with the different versions available on different sites. >> >> On pypi, there is a version 0.6.6: >> https://pypi.python.org/pypi/control/0.6.6 >> >> in Github, the master is in version 0.6.5 >> >> in Sourceforge, the package is in version 0.6d >> >> which version is the correct one? >> >> Thanks, >> >> Emmanuel Sérié. >> >> >> >> >> 2014-08-10 0:37 GMT+02:00 Richard Murray <mu...@cd...>: >> Following a discussion on the developers list, the source code repository and issues tracking for python-control package have been shifted from SourceForge to GitHub. User support for python-control remains on SourceForge, including downloads of the latest release, code documentation, and user discussion lists. >> >> If you are a user of python-control, you can continue to use SourceForge as the primary location of file downloads and user documentation: >> >> http://python-control.sourceforge.net/ >> http://python-control.sourceforge.net/manual/ >> >> The current release of python-control is 0.6d, release on 22 March 2014. A new version should be coming sometime this summer. >> >> In addition to shifting the development environment to GitHub, we have change the python-control-discuss mailing list from a developers-only list to a general discussion list. Feel free to use that list if you want to see discussions about usage of the package: >> >> https://lists.sourceforge.net/lists/listinfo/python-control-discuss >> >> This list (python-control-announce) will continue to be a low-volume mailing list with posts regarding new releases of the package or other major updates. >> >> For those who are interested in the very latest version of python-control, you can clone the python-control project on github: >> >> https://github.com/python-control/python-control >> >> -richard >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> python-control-announce mailing list >> pyt...@li... >> https://lists.sourceforge.net/lists/listinfo/python-control-announce > |
|
From: Scott C. L. <sli...@cd...> - 2014-11-26 23:50:10
|
Authentication is not required. Try
git clone https://github.com/python-control/python-control.git
You can find that repo URL by visiting
https://github.com/python-control/python-control and finding a box
labeled "HTTPS clone URL", which is along the right side on my screen.
2014-11-26 16:30 GMT-05:00 Emmanuel Sérié <es...@gm...>:
> Tanks for the clarification.
> I also noticed that an authentification is needed on github to be able to do a git clone, is it normal?
>
> Emmanuel Sérié
>
|
|
From: Emmanuel S. <es...@gm...> - 2014-11-27 14:57:36
|
Ok, thanks, it's working now for me! It have seemed to me that this command did not worked correctly yesterday... 2014-11-27 0:50 GMT+01:00 Scott C. Livingston <sli...@cd...>: > Authentication is not required. Try > > git clone https://github.com/python-control/python-control.git > > You can find that repo URL by visiting > https://github.com/python-control/python-control and finding a box > labeled "HTTPS clone URL", which is along the right side on my screen. > > > 2014-11-26 16:30 GMT-05:00 Emmanuel Sérié <es...@gm...>: > > Tanks for the clarification. > > I also noticed that an authentification is needed on github to be able > to do a git clone, is it normal? > > > > Emmanuel Sérié > > > |
|
From: Scott C. L. <sli...@cd...> - 2014-11-27 04:08:37
|
Furthermore, the release on PyPI should *not* be 0.6.5. It appears that this was done by someone uploading the tip of master. Relevant discussion appears on issue #19 (https://github.com/python-control/python-control/issues/19#issuecomment-51902320), in particular @jgoppert wrote "I went ahead and uploaded it to pypi since there is no significant difference from what was up there currently." I could not tell from from the context what is being referred to by "it". Unless I am missing something, the best course of action is for someone with admin capabilities to remove 0.6.5 and 0.6.6 and upload 0.6d. The goal is to have the current release as available from PyPI be the same as that available from http://sourceforge.net/projects/python-control/files/ |
|
From: Clancy R. <cwr...@pr...> - 2014-11-27 16:49:28
|
Or another option would be to add a new release to the sourceforge site. This might be better, since I think a number of small things have been fixed (e.g. dare) in the release that is on github, so reverting to the previous version would break these again. Also, it may be worth discussing what the project's "workflow" should be, now that we have moved to github. For instance, we could agree to use the "GitHub Flow" workflow discussed here: https://guides.github.com/introduction/flow/index.html in which we develop new features on side branches, and the master branch is always deployable. This might be nice, as it would be clear what the "current version" is (it is always the master branch). But there are other possible workflows one could use too, for instance as discussed on the bitbucket site: https://www.atlassian.com/git/tutorials/comparing-workflows -clancy > On Nov 26, 2014, at 8:08 PM, Scott C. Livingston <sli...@cd...> wrote: > > Furthermore, the release on PyPI should *not* be 0.6.5. It appears > that this was done by someone uploading the tip of master. Relevant > discussion appears on issue #19 > (https://github.com/python-control/python-control/issues/19#issuecomment-51902320), > in particular @jgoppert wrote "I went ahead and uploaded it to pypi > since there is no significant difference from what was up there > currently." I could not tell from from the context what is being > referred to by "it". > > Unless I am missing something, the best course of action is for > someone with admin capabilities to remove 0.6.5 and 0.6.6 and upload > 0.6d. The goal is to have the current release as available from PyPI > be the same as that available from > http://sourceforge.net/projects/python-control/files/ > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > python-control-developers mailing list > pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-control-developers |
|
From: Richard M. <mu...@cd...> - 2014-11-28 16:51:51
|
I agree that we should think about pushing 0.6.5 out to SourceForge and then we can put that on PyPI as well. I also like the idea of usign the standard GitHub workflow, with new features done in a branch and then a pull request that gets handled by someone other than that branch developer (so that two sets of eyes have a look at it). How about something like this: * We work on releasing 0.6.5 that fixes up a few critical issues (we can flag those in github), but otherwise goes out soon (next few weeks). Version 0.6.5 would then get pushed out to SourceForge and PyPI as an official release, with e-mail to python-control-announce. * We shift to a branch-based workflow where future changes are done on a branch and generate a pull request to this list when ready to be incorporated. Anyone who is interested can comment on the pull request and someone other than the developer eventually does the merge (we can assign someone as part of the pull request process). * While I agree that the master branch should always be deployable, not sure yet whether we should generate a new release (on SourceForge and PyPI) every time someone adds a feature. We could do that at a slower pace and just push out things at the level of "0.7" when we think we have collected enough changes to make a difference. I suggest we try to close on this by 1 Dec (Mon) AoE and then see if there is a consensus on how to move forward. -richard > On 27 Nov 2014, at 7:58 , Clancy Rowley <cwr...@Pr...> wrote: > > Or another option would be to add a new release to the sourceforge site. This might be better, since I think a number of small things have been fixed (e.g. dare) in the release that is on github, so reverting to the previous version would break these again. > > Also, it may be worth discussing what the project's "workflow" should be, now that we have moved to github. For instance, we could agree to use the "GitHub Flow" workflow discussed here: > https://guides.github.com/introduction/flow/index.html > in which we develop new features on side branches, and the master branch is always deployable. This might be nice, as it would be clear what the "current version" is (it is always the master branch). > > But there are other possible workflows one could use too, for instance as discussed on the bitbucket site: > https://www.atlassian.com/git/tutorials/comparing-workflows > > -clancy > >> On Nov 26, 2014, at 8:08 PM, Scott C. Livingston <sli...@cd...> wrote: >> >> Furthermore, the release on PyPI should *not* be 0.6.5. It appears >> that this was done by someone uploading the tip of master. Relevant >> discussion appears on issue #19 >> (https://github.com/python-control/python-control/issues/19#issuecomment-51902320), >> in particular @jgoppert wrote "I went ahead and uploaded it to pypi >> since there is no significant difference from what was up there >> currently." I could not tell from from the context what is being >> referred to by "it". >> >> Unless I am missing something, the best course of action is for >> someone with admin capabilities to remove 0.6.5 and 0.6.6 and upload >> 0.6d. The goal is to have the current release as available from PyPI >> be the same as that available from >> http://sourceforge.net/projects/python-control/files/ >> >> ------------------------------------------------------------------------------ >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> with Interactivity, Sharing, Native Excel Exports, App Integration & more >> Get technology previously reserved for billion-dollar corporations, FREE >> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk >> _______________________________________________ >> python-control-developers mailing list >> pyt...@li... >> https://lists.sourceforge.net/lists/listinfo/python-control-developers > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > python-control-developers mailing list > pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-control-developers |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X