Thread: [myhdl-list] Is it time for 0.9 release?
Brought to you by:
jandecaluwe
From: Christopher F. <chr...@gm...> - 2014-12-30 14:42:29
|
I think it is time for the 0.9 release, the major feature in 0.9 is the interfaces. Some have been using the interfaces for awhile and there are no obvious issues. I think 0.9 could be released, thoughts? Regards, Chris |
From: Jan D. <ja...@ja...> - 2015-02-01 20:57:54
|
On 12/30/2014 03:42 PM, Christopher Felton wrote: > I think it is time for the 0.9 release, the major > feature in 0.9 is the interfaces. Some have been > using the interfaces for awhile and there are no > obvious issues. > > I think 0.9 could be released, thoughts? I agree, but I have not been able to use the new features myself yet. First, do all the tests run? I thought there were still some issues. Most importantly - documentation? There should be something in the manual. And also a whatsnew document so that people know the purpose of the release. I think there is one really major feature and that we should set the spotlight on it to get attention. It's a good example of how we can support functionality which is not necessarily present in the target languages. Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Python as a HDL: http://www.myhdl.org VHDL development, the modern way: http://www.sigasi.com World-class digital design: http://www.easics.com |
From: Keerthan JC <jck...@gm...> - 2015-02-02 03:43:52
|
All the core and verilog tests are passing on my branch. Some VHDL conversion tests are failing on both stable and dev versions. I still need to fine tune the top level ports naming scheme. I think we will be ready for releasing after that. On Sun, Feb 1, 2015 at 3:57 PM, Jan Decaluwe <ja...@ja...> wrote: > On 12/30/2014 03:42 PM, Christopher Felton wrote: > > I think it is time for the 0.9 release, the major > > feature in 0.9 is the interfaces. Some have been > > using the interfaces for awhile and there are no > > obvious issues. > > > > I think 0.9 could be released, thoughts? > > I agree, but I have not been able to use the new features > myself yet. > > First, do all the tests run? I thought there were still > some issues. > > Most importantly - documentation? There should be something > in the manual. And also a whatsnew document so that people > know the purpose of the release. > > I think there is one really major feature and that we > should set the spotlight on it to get attention. It's a > good example of how we can support functionality which > is not necessarily present in the target languages. > > Jan > > -- > Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com > Python as a HDL: http://www.myhdl.org > VHDL development, the modern way: http://www.sigasi.com > World-class digital design: http://www.easics.com > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > -- have a nice day -jck |
From: Christopher F. <chr...@gm...> - 2015-02-03 20:03:56
|
On 2/1/2015 2:57 PM, Jan Decaluwe wrote: <snip> >> I think 0.9 could be released, thoughts? > > I agree, but I have not been able to use the new features > myself yet. > > First, do all the tests run? I thought there were still > some issues. > I had forgotten there was a failing test, as @jck mentioned he has a fix for it. Once he creates a PR we will be good to go with regression tests (I believe). > Most importantly - documentation? There should be something > in the manual. And also a whatsnew document so that people > know the purpose of the release. With the original PR there is a small start to the documentation in the "What's new" section [1], but it needs more! I will look to @jck to provide some details in the conversion section. The interfaces need to be added to the manual as well. Should it have its own section? Or should it be sprinkled throughout the manual, e.g. a mention in the "signal, ports, and concurrency" section [2] and ...? It sounds like we all agree, we can start working towards a release. That is, preparing documentation and smoothing any rough corners. The main feature in this release is *interfaces* MEP107. Regards, Chris [1] https://bitbucket.org/jandecaluwe/myhdl/src/f7a6b2ef05bbf418349d8b0021d81b4fc83b8ce0/doc/source/whatsnew/0.9.rst?at=0.9-dev [2] http://docs.myhdl.org/en/latest/manual/intro.html#signals-ports-and-concurrency |
From: Christopher F. <chr...@gm...> - 2015-02-09 12:16:56
|
>> I think 0.9 could be released, thoughts? There has been some intermingled chatter in other threads on different topics and issues. Below is a subset summary per the relevant topics. 0.9 Release ----------- It sounds like there are no blockades for a 0.9 release and we are moving forward with a 0.9 release. Things that need to been completed: 1. PR from @jck to resolve the failing interface tests. 2. Documentation for interfaces. 3. Normal release stuff. The Move -------- There also has been talk about moving to git/github. I assume this will happen after the 0.9 release, correct? Regards, Chris |
From: Angel E. <ang...@gm...> - 2015-02-09 12:29:32
|
On Mon, Feb 9, 2015 at 1:16 PM, Christopher Felton <chr...@gm...> wrote: >>> I think 0.9 could be released, thoughts? > > There has been some intermingled chatter in other > threads on different topics and issues. Below is > a subset summary per the relevant topics. > > > 0.9 Release > ----------- > It sounds like there are no blockades for a 0.9 > release and we are moving forward with a 0.9 release. > Things that need to been completed: > > 1. PR from @jck to resolve the failing interface > tests. > 2. Documentation for interfaces. > 3. Normal release stuff. > > > The Move > -------- > There also has been talk about moving to git/github. I > assume this will happen after the 0.9 release, correct? Has the move to git/github been decided? It may be a good move in order to get more exposure for the project. However, having used git and github recently for some open source contributions I find that the experience is terrible compared to using mercurial (and BitBucket). I don't get why people like github so much (other than because it is very popular). I find that the BitBucket UI is not as flashy as github's but is IMHO easier to use and mercurial is oh so much simpler than git! Angel |
From: Henry G. <he...@ca...> - 2015-02-09 12:32:12
|
On 09/02/15 12:29, Angel Ezquerra wrote: > I find that the BitBucket UI is not as flashy as > github's but is IMHO easier to use and mercurial is oh so much simpler > than git! I find precisely the opposite. Perhaps it's to do with what tools one is used to. Henry |
From: Angel E. <ang...@gm...> - 2015-02-09 23:31:45
|
On Mon, Feb 9, 2015 at 1:32 PM, Henry Gomersall <he...@ca...> wrote: > On 09/02/15 12:29, Angel Ezquerra wrote: >> I find that the BitBucket UI is not as flashy as >> github's but is IMHO easier to use and mercurial is oh so much simpler >> than git! > > I find precisely the opposite. Perhaps it's to do with what tools one is > used to. It was not my intention to start a mercurial vs git flamewar (hence the "IMHO" qualifier on my statement above). Out of curiosity, which part do you disagree with, the github vs bitbucket part, the git vs mercurial part or both? I'd be inclined to agree with you in that it is a matter of the tool you are used to on the first part. On the second one (git vs mercurial) not so much :P Cheers! Angel |
From: Keerthan JC <jck...@gm...> - 2015-02-10 06:04:01
|
There are failing VHDL tests: https://travis-ci.org/jck/myhdl/jobs/47472029 Are we planning to fix there before 0.9? On Mon, Feb 9, 2015 at 6:31 PM, Angel Ezquerra <ang...@gm...> wrote: > On Mon, Feb 9, 2015 at 1:32 PM, Henry Gomersall <he...@ca...> wrote: > > On 09/02/15 12:29, Angel Ezquerra wrote: > >> I find that the BitBucket UI is not as flashy as > >> github's but is IMHO easier to use and mercurial is oh so much simpler > >> than git! > > > > I find precisely the opposite. Perhaps it's to do with what tools one is > > used to. > > It was not my intention to start a mercurial vs git flamewar (hence > the "IMHO" qualifier on my statement above). > > Out of curiosity, which part do you disagree with, the github vs > bitbucket part, the git vs mercurial part or both? > I'd be inclined to agree with you in that it is a matter of the tool > you are used to on the first part. On the second one (git vs > mercurial) not so much :P > > Cheers! > > Angel > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > -- have a nice day -jck |
From: Christopher F. <chr...@gm...> - 2015-02-10 11:49:01
|
On 2/10/15 12:03 AM, Keerthan JC wrote: > There are failing VHDL tests: https://travis-ci.org/jck/myhdl/jobs/47472029 > > Are we planning to fix there before 0.9? > That is a good question, I am not sure. Typically I would say of course but these tests also fail on 8.1 (see below). We could mark it as something todo maybe for a 9.1 release. At this point I don't know why they are failing or what it might take to fix them. This would seem reasonable to me (postpone the fix). Regards, Chris >>> import myhdl >>> myhdl.__version__ '0.8.1' >> ghdl --version GHDL 0.29 (20100109) [Sokcho edition] Compiled with GNAT Version: 4.6 GCC back-end code generator Written by Tristan Gingold. >> py.test GHDL.py test_*.py ============================= test session starts ============================== platform linux2 -- Python 2.7.5 -- pytest-2.3.5 collected 83 items test_adapter.py . test_AssignSignal.py . test_bin2gray.py .. test_case.py .... test_constants.py . test_dec.py .... test_errors.py ... test_fsm.py . test_hec.py . test_inc.py ..... test_intbv_signed.py ... test_listofsigs.py ............ test_loops.py ............... test_method.py ... test_nonlocal.py . test_numass.py . test_print.py ...... test_ram.py ..... test_rom.py .... test_ShadowSignal.py .F.. test_ternary.py F. test_toplevel_method.py .... =================================== FAILURES =================================== ______________________________ test_ConcatSignal _______________________________ def test_ConcatSignal(): > assert conversion.verify(bench_ConcatSignal) == 0 E assert 1 == 0 E + where 1 = <myhdl.conversion._verify._VerificationClass object at 0x2e2ba50>(bench_ConcatSignal) E + where <myhdl.conversion._verify._VerificationClass object at 0x2e2ba50> = conversion.verify test_ShadowSignal.py:60: AssertionError ------------------------------- Captured stderr -------------------------------- bench_ConcatSignal.vhd:45:19: constant "i" is not visible here bench_ConcatSignal.vhd:46:23: constant "j" is not visible here bench_ConcatSignal.vhd:47:27: constant "k" is not visible here bench_ConcatSignal.vhd:48:31: constant "m" is not visible here bench_ConcatSignal.vhd:49:37: prefix is neither a function name nor can it be sliced or indexed bench_ConcatSignal.vhd:50:30: prefix is neither a function name nor can it be sliced or indexed bench_ConcatSignal.vhd:51:37: prefix is neither a function name nor can it be sliced or indexed bench_ConcatSignal.vhd:52:37: prefix is neither a function name nor can it be sliced or indexed /usr/lib/ghdl/bin/ghdl: compilation error Analysis failed ________________________________ test_ternary1 _________________________________ def test_ternary1(): > assert conversion.verify(TernaryBench, ternary1) == 0 E assert 1 == 0 E + where 1 = <myhdl.conversion._verify._VerificationClass object at 0x2e2ba50>(TernaryBench, ternary1) E + where <myhdl.conversion._verify._VerificationClass object at 0x2e2ba50> = conversion.verify test_ternary.py:69: AssertionError ------------------------------- Captured stderr -------------------------------- TernaryBench.vhd:63:28: ';' is expected instead of 'when' /usr/lib/ghdl/bin/ghdl: compilation error Analysis failed ===================== 2 failed, 81 passed in 57.23 seconds ===================== |
From: Jan D. <ja...@ja...> - 2015-02-13 19:03:16
|
On 02/10/2015 07:03 AM, Keerthan JC wrote: > There are failing VHDL tests: https://travis-ci.org/jck/myhdl/jobs/47472029 > > Are we planning to fix there before 0.9? I have to review the ternary operator test. This was in anticipation of VHDL-2008, but now I'm not sure it's official VHDL. As for the other tests, the tests that fail at my side are different than yours (on github). Seems you fixed test_interfaces3.py, but another test related to ShadowSignals now fails. The goal for 0.9 should definitely be no failing tests. Jan > On Mon, Feb 9, 2015 at 6:31 PM, Angel Ezquerra <ang...@gm... <mailto:ang...@gm...>> wrote: > > On Mon, Feb 9, 2015 at 1:32 PM, Henry Gomersall <he...@ca... <mailto:he...@ca...>> wrote: > > On 09/02/15 12:29, Angel Ezquerra wrote: > >> I find that the BitBucket UI is not as flashy as > >> github's but is IMHO easier to use and mercurial is oh so much simpler > >> than git! > > > > I find precisely the opposite. Perhaps it's to do with what tools one is > > used to. > > It was not my intention to start a mercurial vs git flamewar (hence > the "IMHO" qualifier on my statement above). > > Out of curiosity, which part do you disagree with, the github vs > bitbucket part, the git vs mercurial part or both? > I'd be inclined to agree with you in that it is a matter of the tool > you are used to on the first part. On the second one (git vs > mercurial) not so much :P > > Cheers! > > Angel > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > myhdl-list mailing list > myh...@li... <mailto:myh...@li...> > https://lists.sourceforge.net/lists/listinfo/myhdl-list > > > > > -- > have a nice day > -jck > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > > > > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Python as a HDL: http://www.myhdl.org VHDL development, the modern way: http://www.sigasi.com World-class digital design: http://www.easics.com |
From: Christopher F. <chr...@gm...> - 2015-02-13 19:58:08
|
On 2/13/2015 12:28 PM, Jan Decaluwe wrote: > On 02/10/2015 07:03 AM, Keerthan JC wrote: >> There are failing VHDL tests: https://travis-ci.org/jck/myhdl/jobs/47472029 >> >> Are we planning to fix there before 0.9? > > I have to review the ternary operator test. This was in anticipation > of VHDL-2008, but now I'm not sure it's official VHDL. > > As for the other tests, the tests that fail at my side are different > than yours (on github). Seems you fixed test_interfaces3.py, > but another test related to ShadowSignals now fails. > > The goal for 0.9 should definitely be no failing tests. > > Jan > When I tested 0.8.1 with no modifications I had a ShadowSignal failure: >> py.test GHDL.py test_*.py <snip> test_ShadowSignal.py .F.. test_ternary.py F. Regards, Chris |
From: Christopher F. <chr...@gm...> - 2015-02-14 13:43:57
|
> > When I tested 0.8.1 with no modifications I had a > ShadowSignal failure: > > >> py.test GHDL.py test_*.py > <snip> > test_ShadowSignal.py .F.. > test_ternary.py F. > That was incomplete, wanted 0.8.1 to be the baseline. This is the results for testing the latest 0.9-dev on my system: >> py.test GHDL.py test_*.py test_interfaces3.py ..FF test_ShadowSignal.py .F.. test_ternary.py F. >> py.test vcom.py test_*.py test_interfaces3.py ..FF test_ternary.py F. >> py.test Icarus.py test_*.py test_interfaces3.py ..FF Regards, Chris |
From: Keerthan JC <jck...@gm...> - 2015-02-18 07:16:40
|
Jan, Is it safe for me to fork your github repo and apply my commits on it or should I send a PR to bitbucket? On Sat, Feb 14, 2015 at 8:43 AM, Christopher Felton <chr...@gm...> wrote: > > > > > When I tested 0.8.1 with no modifications I had a > > ShadowSignal failure: > > > > >> py.test GHDL.py test_*.py > > <snip> > > test_ShadowSignal.py .F.. > > test_ternary.py F. > > > > That was incomplete, wanted 0.8.1 to be the baseline. > This is the results for testing the latest 0.9-dev > on my system: > > >> py.test GHDL.py test_*.py > test_interfaces3.py ..FF > test_ShadowSignal.py .F.. > test_ternary.py F. > > >> py.test vcom.py test_*.py > test_interfaces3.py ..FF > test_ternary.py F. > > >> py.test Icarus.py test_*.py > test_interfaces3.py ..FF > > > Regards, > Chris > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > -- have a nice day -jck |
From: Jan D. <ja...@ja...> - 2015-02-22 09:15:13
|
On 02/18/2015 08:16 AM, Keerthan JC wrote: > Jan, > Is it safe for me to fork your github repo and apply my commits on it Keerthan: We are on git/github now with an up-to-date repo and development guide. Let's go ahead. Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Python as a HDL: http://www.myhdl.org VHDL development, the modern way: http://www.sigasi.com World-class digital design: http://www.easics.com |
From: Christopher F. <chr...@gm...> - 2015-02-22 19:09:52
|
On 2/22/15 3:14 AM, Jan Decaluwe wrote: > On 02/18/2015 08:16 AM, Keerthan JC wrote: >> Jan, >> Is it safe for me to fork your github repo and apply my commits on it > > Keerthan: > > We are on git/github now with an up-to-date repo and development > guide. Let's go ahead. > > Jan > Since we are going full speed with github, Keerthan should push the travis-CI scripts. Can see the test results on the main repo page :) Regards, Chris |
From: Jan D. <ja...@ja...> - 2015-02-22 19:37:56
|
On 02/22/2015 08:09 PM, Christopher Felton wrote: > On 2/22/15 3:14 AM, Jan Decaluwe wrote: >> On 02/18/2015 08:16 AM, Keerthan JC wrote: >>> Jan, >>> Is it safe for me to fork your github repo and apply my commits on it >> >> Keerthan: >> >> We are on git/github now with an up-to-date repo and development >> guide. Let's go ahead. >> >> Jan >> > > Since we are going full speed with github, Keerthan > should push the travis-CI scripts. Can see the test > results on the main repo page :) I am sure he will but give the guy a break :-) (He has to use some git magic to add unrelated commits to the repo.) -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Python as a HDL: http://www.myhdl.org VHDL development, the modern way: http://www.sigasi.com World-class digital design: http://www.easics.com |
From: Christopher F. <chr...@gm...> - 2015-02-09 13:04:38
|
On 2/9/2015 6:29 AM, Angel Ezquerra wrote: <snip> >> >> The Move >> -------- >> There also has been talk about moving to git/github. I >> assume this will happen after the 0.9 release, correct? > > Has the move to git/github been decided? There is definite momentum in that direction, I believe it is inevitable. > It may be a good move in order to get more exposure for the > project. I don't believe that is the current rationale. > However, having used git > and github recently for some open source contributions I find that the > experience is terrible compared to using mercurial (and BitBucket). I > don't get why people like github so much (other than because it is > very popular). Unfortunately, these conversations are muddle because two things are simultaneously discussed: the version control tool and the web platform. I am unaware of the technical arguments at this point, but if the main developers have a strong preference for git it is hard to argue against it. As a community we want to make development as easy as possible. From my perspective, this means: first, supporting the main developers; second, outlining the process for new developers (both of these occur in MyHDL). If the pro-hg'ers were the highest contributors then there might be precedence for discussion but that is not the current situation. > I find that the BitBucket UI is not as flashy as > github's but is IMHO easier to use and mercurial is oh so much simpler > than git! I agree and I am dreading having to invest the time to figure out some of the more cryptic commands. But since so many projects use git, this investment is not a waste. Hopefully I can avoid past major faux pas with git :) The biggest discomfort for me is not being able to clone to a dropbox folder (or at least not easily). In addition, one of arguments is the use of CI. Since MyHDL has good collection of tests and follows a test-driven mantra, having an integrated CI is nice. I know drone.io exists for bitbucket but someone would need to show a working CI on bitbucket the same as some have done for travis-ci. In the end, as often stated, one of the best ways to support MyHDL is to develop projects with it. Each developer can always choose which platform to host the project. I am sure there will be more on this topic in the future. Regards, Chris |
From: Jan D. <ja...@ja...> - 2015-02-09 22:13:14
|
On 02/09/2015 01:16 PM, Christopher Felton wrote: >>> I think 0.9 could be released, thoughts? > > There has been some intermingled chatter in other > threads on different topics and issues. Below is > a subset summary per the relevant topics. > > > 0.9 Release > ----------- > It sounds like there are no blockades for a 0.9 > release and we are moving forward with a 0.9 release. > Things that need to been completed: > > 1. PR from @jck to resolve the failing interface > tests. > 2. Documentation for interfaces. > 3. Normal release stuff. Correct. > The Move > -------- > There also has been talk about moving to git/github. I > assume this will happen after the 0.9 release, correct? For a variety of reasons, I have basically decided to git eventually, probably sooner than later. I have not decided when exactly, I am working with @jck to sort that out. Note that git is also more prominent than mercurial on bitbucket, people who prefer that interface can use still use it for their primary repo's. @Chris - if you have documentation for 0.9 in your recent fork, I will gladly pull it in of course. Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Python as a HDL: http://www.myhdl.org VHDL development, the modern way: http://www.sigasi.com World-class digital design: http://www.easics.com |
From: David B. <dav...@ya...> - 2015-02-09 22:24:21
|
I was wondering if anyone out there would be interested in receiving a white paper from me regarding my attempts at developing a kick-starter project (kickstarter.com) for the MyHDL environment ??? Is anyone interested ??? Thanks, David Blubaugh |