search

kutsurak / python-bitstring

Automatically exported from code.google.com/p/python-bitstring
0 stars 0 forks source link

Issue with current version #125

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi,

There is an issue with the new version. I have an evolutionary computation 
application  which was working perfectly with bitstring 2.2, and when I changed 
to version 3.0.2 stopped being able to evolve.

The problem is I don't know where to look for the bug, but I am sure it is a 
bitstring issue. I have tested with python2.6 & bitstring 2.2 (old packaging), 
and everything works perfectly. If I try with python 2.7 & bitstring 3.0.2 and 
evolution is stuck.

I would like some opinions/effort from the developers to know what has changed 
and could be the cause of the problem. For instance, are there any new caches, 
and I am eventually loosing modifications on the strings?

Thanks in advance
RL

What's the problem? (If this is a feature request then feel free to delete
all the questions and just say what you want!)

What is the expected output? What do you see instead?

Which version of bitstring are you using (bitstring.__version__), which
version of Python (e.g. 2.7, 3.2) and what platform
(Linux, Windows, etc.)

Please provide any additional information below.

Original issue reported on code.google.com by rui.lour...@gmail.com on 24 May 2012 at 3:57

GoogleCodeExporter commented 9 years ago 
Hi, 

You can check the changes in 3.0 in the release notes 
(http://packages.python.org/bitstring/release_notes.html) but the only 
significant one in terms of backwards compatibility is the change to the 
meaning of step in slicing notation (and your problem doesn't sound like that, 
probably).

There have been changes to caching, but there are no known issues.

Difficult to say without seeing the code. If you have something that I can test 
then I can do that. Just email me (scott@griffiths.name) and I can take a look. 
Otherwise if you can get any sample piece of code that behaves differently with 
the different versions then that would work too.

Cheers,

Scott

Original comment by dr.scott...@gmail.com on 24 May 2012 at 4:05

GoogleCodeExporter commented 9 years ago 
Hi Scott,

Gladly I found it quick, it was due to the removal of the prefix in the 
attributes (.bin, etc).
Sorry for the issued issue :)

Cheers
RL

Original comment by rui.lour...@gmail.com on 24 May 2012 at 7:22

GoogleCodeExporter commented 9 years ago

Original comment by dr.scott...@gmail.com on 28 May 2012 at 12:12