Pythoscope 0.6-basic-side-effects

Differentiate between pure and "side effecty" code.

As we slowly move into the domain of code with side effects first thing we'll need is a method to differentiate "pure" code from a "side effecty" one. For all practical purposes we'll treat any code that doesn't effect the outside world in any way as pure. Whether it assigns values or destructively modifies its local variables doesn't matter to us, as long as it keeps those operations encapsulated. Sample sources of side effects we're interested in are global/class variables, file system, databases, and IO operations. Finding whether a module is import-safe may also be a possible problem we can spend a time on.

Milestone information

Project:
Pythoscope
Series:
trunk
Version:
0.6-basic-side-effects
Expected:
 
Active:
Yes. Drivers can target bugs and blueprints to this milestone.  

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
4 Not started
Bugs:
No bugs are targeted to this milestone.

4 blueprints and 0 bugs targeted

Blueprint Priority Assignee Delivery
Shared state descriptors Shared state descriptors 3 Medium   1 Not started
Find safe callables in user's code Find safe callables in user's code 3 Medium   1 Not started
Import safety Import safety 3 Medium   1 Not started
Object attributes side effects Object attributes side effects 3 Medium   1 Not started
This milestone contains Public information
Everyone can see this information.